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

Adjusted phase lines for MadMax progress calculations #1258

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

tivikoff
Copy link

Hello. I noticed that in windows MadMax stotik's fork actual phase line ends are different in the logs. And what I see is that they should not include backend_header_lines value (which is not 11 but 15 in my case). This produced wrong percentage calculations in the viewer.
As I mentioned header takes 15 lines and Phase 1 end is actually at line 23. Based on the code this header should be taken into account, but something strange happens with the math, and percentage shows correctly only if I manually substract header lines from each phase ends and put these numbers in the config. So 23-15 = 8 etc.
Also phase weights for MadMax are different than for original plotter, I adjusted weights based on my 4 different 12-20 threads PCs logs.

In windows MadMax stotik's fork logs produces 15 lines of header before Phase 1 starts. This value may be variable (based on how much extra -2 -d -u parameters you've specified), but in the most common scenarios it's around 15. In ideal scenario it should be included in the config progress parameters, so the user itself be able to adjust it for it's personal logs. Currently, original value "madmax=11" produces wrong percentage progress calculations in the viewer.
In windows MadMax stotik's fork actual phase line ends are different. They should not include backend_header_lines value (which is not always 11 (more often is 15) in log.py, should be also corrected). This produced wrong percentage calculations in the viewer.
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

Successfully merging this pull request may close these issues.

None yet

1 participant