CWorthy-ocean / C-Star

5 stars 3 forks source link

Progress tracking #20

Open TomNicholas opened 3 weeks ago

TomNicholas commented 3 weeks ago

Even running the small roms_marbl example is taking a few minutes on my mac. Without being familiar with ROMS/Marbl command-line output it's hard to know how far through the computation it has progressed. Some kind of progressbar would be nice for this, but I don't know how tricky that would be to interface with ROMS/marbl.

dafyddstephenson commented 3 weeks ago

This also covers the issue of job management on HPC systems. C-Star can submit a job to a queue, but currently has no access to information on whether that job is running, queued, or complete. Future versions should allow the user to query basic information about job status, and ideally (as raised by this issue) progress.

As an aside, the example in the notebook isn't really small as it's running for a month with a 6 minute time step. For comparison the CI test runs for 30 model minutes. I'd expect the notebook test to run for about 15 minutes real time. For now maybe it'd be better to cut the run length down to a model day or two.

TomNicholas commented 3 weeks ago

I think job management could be abstracted out as part of #26