Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
F
Finetuning LLMs for Text2SQL
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Till-Ole Herbst
Finetuning LLMs for Text2SQL
Commits
db80e499
Commit
db80e499
authored
7 months ago
by
Till-Ole Herbst
Browse files
Options
Downloads
Patches
Plain Diff
Update README.md
parent
783ee5bd
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+39
-0
39 additions, 0 deletions
README.md
with
39 additions
and
0 deletions
README.md
+
39
−
0
View file @
db80e499
...
...
@@ -106,4 +106,43 @@ echo "Time elapsed: ${hour} hour $min min " >>${pred_log}
## Job auf GPU legen
siehe
```batch_pipeline.sh```
```
#!/bin/bash
#SBATCH --job-name=pipe1
#SBATCH --gres=gpu:1
#SBATCH --cpus-per-gpu=8
#SBATCH --mem-per-cpu=4G
cd
/path/to/repo
source
dbgpt-hub/bin/activate
sh pipeline.sh
```
```
--gres=gpu:1``` ist dabei die Anzahl der angeforderten GPUs
```/path/to/repo``` anpassen
Dann mit ```sbatch``` Job auf GPU legen:
```
sbatch --nodelist=workg01 batch_pipeline.sh
```
Zur Wahl stehen zurzeit ```workg01``` (40GB/GPU) und ```workg02``` (80GB/GPU) mit jeweils 4 GPUs
Mit ```squeue``` können dann laufende Jobs gecheckt werden
## Evaluation
```
cd Spider
python spider/evaluation.py --gold [gold file] --pred [predicted file] --etype [evaluation type] --db [database dir] --table [table file]
arguments:
[gold file] gold.sql file where each line is
`a gold SQL \t db_id`
[predicted file] predicted sql file where each line is a predicted SQL
[evaluation type] "match" for exact set matching score, "exec" for execution score, and "all" for both
[database dir] directory which contains sub-directories where each SQLite3 database is stored
[table file] table.json file which includes foreign key info of each database
Bsp.:
python spider/evaluation.py --gold dev_gold.sql --pred ../output/pred/pred_sqlcoder_llama3_2.sql --etype "match" --db database --table tables.json
\ No newline at end of file
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment