Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: progress bar #141

Open
physicsnerd opened this issue Jun 11, 2024 · 3 comments
Open

Feature request: progress bar #141

physicsnerd opened this issue Jun 11, 2024 · 3 comments

Comments

@physicsnerd
Copy link

physicsnerd commented Jun 11, 2024

When running FDTD.Run, it'd be great if there was some sort of progress bar so I could tell where my simulation was at/whether it was a lost cause. (I'm running in Python.)

@thliebig
Copy link
Owner

If you have a good idea what that progress bar should track let me know. I'm doing FDTD for 20+ years now and I currently would have no idea ;)

Tracking e.g. steps vs max. number steps is bad because you should always set max number of steps way to large and let the energy decrement decide when to stop. Therefore you never know beforehand at what number of steps a simulation is done.
And tracking the energy decay (decrement) does not really work either, because first the energy rises and then it decays uneven. Most of the time quick at first and (much) slower later...

But as I said, any ideas are welcome...

@physicsnerd
Copy link
Author

I think tracking, for instance, both of these would be reasonable - I'm aware the max steps is not actually when the simulation will be done and the energy decay is not monotonic, but this is more a feature request for a sanity check that, e.g., each step isn't taking way too long, or that the energy decay isn't occurring excessively slowly, or even how close one is to the max number of steps. Maybe this is less a progress bar in the sense of 'towards completion' and more a progress bar in the sense of 'progress is occurring at a reasonable rate' haha.

@biergaizi
Copy link
Contributor

Also, as we're on it... The current simulation progress shows speed in "seconds per timestep". But this number is usually too small to read. I think it's better to change this to "timesteps per second", which has better readability. If it says "1000 timesteps per second", everyone can do some basic mental math to guess how long it's going to run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants