`Tidy3DWebRunnerNode` doesn't require the visibility of a cost estimate before running a simulation #41

New Issue

Open

opened 2024-05-05 09:28:50 +02:00 by so-rose · 0 comments

so-rose commented

2024-05-05 09:28:50 +02:00

Owner

It's critical that the user be guaranteed informed about how much running a particular simulation will cost. Therefore, is_task_runnable should also check that estimated cost.

It's not done so far, because caching of estimated cost isn't something currently done in tdcloud.CloudTaskInfo (it's currently just a callable). We could look into a @cached_property, since in most cases, Tidy3DWebExporterNode will perform the expensive cost estimation, and hand that object off directly - causing the instance to reuse the estimated cost value.

It's critical that the user be guaranteed informed about how much running a particular simulation will cost. Therefore, `is_task_runnable` should also check that estimated cost. It's not done so far, because caching of estimated cost isn't something currently done in `tdcloud.CloudTaskInfo` (it's currently just a callable). We could look into a `@cached_property`, since in most cases, `Tidy3DWebExporterNode` will perform the expensive cost estimation, and hand that object off directly - causing the instance to reuse the estimated cost value.