search

lizzieinvancouver / temporalvar

0 stars 0 forks source link

new batch of megaD runs #33

Closed donahuem closed 5 years ago

donahuem commented 5 years ago

Each of the three MegaD cases were sent with 20 tasks in each array and 200 runs per task. Job IDs: 58137170 58137225 58137269

donahuem commented 5 years ago

These did not write completely - assuming because we ran out of space on scratch drive. Set a new batch of 3 arrays of 50 tasks each with 100 runs per task 58378327 58378360 58378361

donahuem commented 5 years ago

These have completed, although not all runs were written bc of memory issues. But ready to pull. Will start another batch.

donahuem commented 5 years ago

Next batch (50 tasks of 100 runs) 58551618 58551687 58551741

donahuem commented 5 years ago

I had assumed that scratch was separate for each node and named the scratch folder by the jobID. If it is shared, then the first job to finish might be moving all files in the jobID folder. Instead, name folder by jobID-taskID. Rerunning: Submitted batch job 58582169 Submitted batch job 58582192 Submitted batch job 58582223

donahuem commented 5 years ago

These ran all the way through