it would be nice if there were timestamps on each step in the iterative algorithm ... i have a job running for a couple days, i can see it is converging around 20 steps per calculation, but i have no timestamp on each step, so i have to grep my log, count the number of steps, and make an estimate .. too much work ... at least if i knew, for example, it seems to be converging at 20 steps, and each step takes 20 minutes, then i can make some sort of rough estimate based on those assumptions, how long it will continue to run for ...
although i am sure we all (including you) would love for calculations to run in minutes, my experience is that I have to plan my entire week around what i have running and when they might finish .. this is a reality of doing this type of simulation .. i have a tfet tansmission calc running for over 3 days, for example ... will it be another 3 days? or a few more hours? i have no idea until a few transmission calcs are done, and i get a timestamp on those ... until then i am in the dark unless i make my own estimates
