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

Cosmetics in Progression Bar in Deconvolution #6

Open
gordonkoehn opened this issue Dec 19, 2024 · 1 comment · May be fixed by #7
Open

Cosmetics in Progression Bar in Deconvolution #6

gordonkoehn opened this issue Dec 19, 2024 · 1 comment · May be fixed by #7
Assignees
Labels
bug Something isn't working

Comments

@gordonkoehn
Copy link
Contributor

gordonkoehn commented Dec 19, 2024

Lollipop v0.5.1 introduced independent progression bars for different locations in the multiprocessing.

It appears when one location is processed only, the progression bar does not behave as it should.

If more than one core is given with --n-core the progression bars are fine – it is progressively updated in the same line.

If just one core is given, as it should the progression bar seems to be rewritten for each update, leaving the last state in the line above. See below:

Screenshot 2024-12-19 at 09 46 40

This behaviour should be avoided, and it should be possible as the number of cores is set to one for one location.

This is behaviour on OSX.

@gordonkoehn gordonkoehn added the bug Something isn't working label Dec 19, 2024
@gordonkoehn gordonkoehn changed the title Progression Bar in Deconvolution – repeating for one location 1 core. Cosmetics in Progression Bar in Deconvolution Dec 19, 2024
@gordonkoehn
Copy link
Contributor Author

gordonkoehn commented Dec 19, 2024

This issue happens to be addressed by

@gordonkoehn gordonkoehn self-assigned this Dec 19, 2024
@gordonkoehn gordonkoehn assigned DrYak and unassigned gordonkoehn Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants