% Done Monitoring

[tylerflex]

So this is looking pretty good on the front end, but needs some testing and a bit of refinement.

How it works now:

1. Use console.status (running man animation) to loop through pre-processing statuses.
2. Log that the solver is starting until we can successfully grab the % done data.
3. Progressbar through % done and print field_Decay in progress bar description.
4. Use console.status (running man animation) to loop through post-processing statuses

Simplifies a lot.
Job uses web.monitor() now.

Remaining issues:

• Takes a long time to start getting % done, by which point the task is already completed. Need to either reduce this amount of time or change the message.
• Needs some more testing by us before I feel confident releasing it.

[tylerflex]

issue #140

[momchil-flex]

This is pretty decent for tasks that take longer than a minute. I'm down to merge - is there any specific testing you have in mind? Let's check in with Lei again about making the solver_progress.csv available earlier than after 100s.

Just one thing maybe to fix, this ran to 32% before early shutoff, but then it shows 100% done. Should we fix that?

[tylerflex]

Yea I think it marks the progress bar as "complete" when it's done running. I dont know if it would be more confusing to leave like this or to change it to end at 32% (potentially making people think the job didn't finish). What do you think?

[tylerflex]

No specific testing in mind, just wanted to get another pair of eyes on it.

[momchil-flex]

Yea I think it marks the progress bar as "complete" when it's done running. I dont know if it would be more confusing to leave like this or to change it to end at 32% (potentially making people think the job didn't finish). What do you think?

I feel like given that this is the full output, it won't be confusing, and it would provide the extra information about at what point the shutoff happened.

[tylerflex]

Ok I pushed this fix. If it's no longer running but the perc_done < 100 it will just display the message about early shutoff and leave the progress bar where it was. If it's no longer running but perc_done >= 100 it will explicitly set the progress bar to "completed" like you see in all cases before this change.

[momchil-flex]

Alright Lei pushed the change to get solver_progress in the first 10s. I tried a simulation that took 33s total and it worked pretty well! OK to merge as far as I'm concerned.

[momchil-flex]

Oh, sorry, it does seem to print "success" twice

[momchil-flex]

Also, in old tidy3d, in the monitor function, we do something like status = "success" if status == "visualize" and we don't print "visualize" as a status. This is because this step is the exporting of images (the three cross sections so far) on the server side, but the simulation data is already available to the user before this step is finished.

[tylerflex]

ok my last commit should do it, I refactored out the get_status() operation and made it return success if visualize. Then, I fixed a minor bug where the shutoff message wasn't getting displayed in a weird edge case. I also checked on a few notebooks that this works as expected.