Closed nickwg03 closed 4 years ago
I think this might be an eagle bug. I can't get jobs to submit either. I have a ticket in. Also what is up with that directory name!??!
@MRossol it's a batch run, which is why the dirname is so long.
I was doing fine up until the QA-QC stage. I had run aggregation, supply curve, rep profiles, and finally at QA-QC it would fail, but not always. When I'd run 1 of the batch runs it sometimes works, sometimes doesn't.
@nickwg03 it doesn't look like you included qa-qc in the batch config:
"files": [
"./config_aggregation.json",
"./config_supply-curve.json",
"./config_rep-profiles.json"
],
Issues was that multiple jobs were using the same job name.
@MRossol fixed the QAQC module to use the appropriate name for each job.
Bug Description I'm trying to run the exclusion layer QA-QC module, but the submission will hang for a while and then return a message that the job couldn't kick-off (in the .log file) and refers the user to check the stdout file, but no stdout file is created for the job.
I've had trouble getting the exclusion layer QA-QC module to run in the past, usually requiring a few attempts to get it to run (especially when running several jobs at the same time via the batch approach). I notice that the "name" is always 'reV' when running the exclusion layer QAQC, so I'm wondering if the duplicative name is causing it to be hung up?
Full Traceback
But then as noted above, no stdout file is created.
To Reproduce Check outputs at
/shared-projects/rev/projects/heco/rev/agg_batched/run_pv_fixed_afk0_ma01_gf0_pd36_rcd0_rf0_td0_fcr0052_ay0_ed0
on Eagle.Charge code WTSA.11658.01.01.01