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

Peak fit parallelization #766

Closed
borondics opened this issue Oct 31, 2024 · 6 comments
Closed

Peak fit parallelization #766

borondics opened this issue Oct 31, 2024 · 6 comments

Comments

@borondics
Copy link
Member

Since we have problems with the parallel fitting I was thinking if we could simply use Dask for this?

@stuart-cls
Copy link
Member

As far as I know, the problem is fixed (#748)! If not, we need a new bug :)

Dask is another good option for parallelization but we don't have dask in our standard release.

@borondics
Copy link
Member Author

Yes, it is working now, but only using one core, right?

@stuart-cls
Copy link
Member

Two processes by default, but you can override on beefier machines by setting an environment variable:

By default this is limited to 2 extra processes, but this can be
overridden by setting the environment variable QUASAR_N_PROCESSES to the desired number, or all
to use the default value returned by os.cpu_count().

I put it in the docs but it's not showing up on https://orange-spectroscopy.readthedocs.io/en/latest/widgets/peakfit.html 🧐

@stuart-cls
Copy link
Member

Fixed the readthedocs.

@markotoplak
Copy link
Collaborator

Thanks, @stuart-cls.

@borondics
Copy link
Member Author

@stuart-cls, I was just thinking about this environment variable. Would it make more sense to have a setting somewhere in Quasar? Either in the menu or the widget itself?

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