You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The back-end returns this value, it is not a front-end issue.
Also, this is not reproductible: using the log_parser.py on the log file does return a value below 100%.
My guess based on what I saw, is that the launch_progress_dto.coef that's supposed to be 0.8 (and stay like this) can become 800 whithout any apparent reason
What's asked
On the long term, we expect the simulator to log this type of line : [Thu Jul 27 14:08:52 2023][solver][infos] Job completion XX%
When it will, we will simplify the parser to use only this value.
For now, we expect AntaresWeb to show job progress less than 100%.
The text was updated successfully, but these errors were encountered:
Description
Example of a job progress way over 100%
The back-end returns this value, it is not a front-end issue.
Also, this is not reproductible: using the log_parser.py on the log file does return a value below 100%.
My guess based on what I saw, is that the
launch_progress_dto.coef
that's supposed to be 0.8 (and stay like this) can become 800 whithout any apparent reasonWhat's asked
On the long term, we expect the simulator to log this type of line :
[Thu Jul 27 14:08:52 2023][solver][infos] Job completion XX%
When it will, we will simplify the parser to use only this value.
For now, we expect AntaresWeb to show job progress less than 100%.
The text was updated successfully, but these errors were encountered: