wasciutto
commented
1 year ago - putting stuff into database
- may need to lock db
- all l1 jobs have these IDs
- table of job IDs
- refresh_feat_status() - doesn't deal with jobs but does go into feat folders and look for dot files
- read_df_sql_r()
- run_glm_pipeline() - create job ids
- design table that will be extensible and is called by the run_glm_pipeline
- r batch job class
Track when jobs are spawned
Needs to be split in sub-tasks