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

Make runMonitoring take more types #2380

Open
mesmith75 opened this issue Aug 27, 2024 · 8 comments
Open

Make runMonitoring take more types #2380

mesmith75 opened this issue Aug 27, 2024 · 8 comments

Comments

@mesmith75
Copy link
Contributor

Currently runMonitoring only takes job slices. Would be nice to have it accept an int, or a list of int or a job object.

@SreeSharvesh
Copy link

Hi! I would like to solve this issue....Can you assign it to me??

@egede
Copy link
Member

egede commented Sep 2, 2024

Hi! I would like to solve this issue....Can you assign it to me??

You are welcome to submit a pull request. Please create a fork, fix the issue and update TestMonitoring.py to include tests that demonstrates that it is working.

@saadkhi
Copy link

saadkhi commented Oct 9, 2024

Hi @egede, if this issue is still open I would to work on it.

@egede
Copy link
Member

egede commented Oct 9, 2024

Yes, you are welcome. See my comment above on how to do this.

@saadkhi
Copy link

saadkhi commented Oct 15, 2024

I can't able to understand what is "runMonitoring", can you briefly tell where I can find it.

@egede
Copy link
Member

egede commented Oct 15, 2024

Usually in Ganga, the progress of jobs is monitored in a background thread. However, Ganga can be started without this thread running and then the runMonitoring function defined in the global name space can be used to monitor a specific set of jobs. See definition and the addition to the global name space. For a general overview of what jobs are and how Ganga works, see the manual.

@Sunnykumar926
Copy link

Hi @egede, this issue is still open, I would like to resolve it

@egede egede linked a pull request Nov 4, 2024 that will close this issue
@egede
Copy link
Member

egede commented Nov 4, 2024

Hi @egede, this issue is still open, I would like to resolve it

No, this one is actually currently being worked on (see #2390)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants