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

stopping Factor during facetimage #202

Open
AHorneffer opened this issue Mar 22, 2017 · 7 comments
Open

stopping Factor during facetimage #202

AHorneffer opened this issue Mar 22, 2017 · 7 comments

Comments

@AHorneffer
Copy link
Contributor

When Factor is running the facetimage pipelines it cannot easily be stopped. Just pressing <CTRL-C> on the command-line will only stop the current facet - which will "fail" - but then runfactor will continue with the next facet and so on.

Even if one wants to continue imaging the next facet if one facet fails, there should be a way top stop Factor when doing facetimage pipelines.

@mhardcastle
Copy link
Collaborator

ctrl-Z, kill %1 ? :)

@AHorneffer
Copy link
Contributor Author

Is that different from <CTRL-C>?

@mhardcastle
Copy link
Collaborator

I think ctrl-z will stop the parent process, and kill %1 will kill it.

@mhardcastle
Copy link
Collaborator

(obviously mutatis mutandis if you have other suspended processes)

@AHorneffer
Copy link
Contributor Author

Well, I just noticed that my Factor runs probably only stopped during selfcal because I set exit_on_selfcal_failure = True

General question: is it actually desirable to continue with the processing if one of the pipelines fails? ("fails" as in: a program in there crashes.)

@soumyajitmandal
Copy link

Probably I am facing similar issue (?). Apparently my job is stuck at the facetimage step (step 5 of 5).
I went to the node and used:
pkill -u mandal

Still running checkfactor is showing 'processing' that facet.

@AHorneffer
Copy link
Contributor Author

Did you also kill the original runfactor processes? (The first one and its child.) If so, then what do checkfactor just didn't get the notice that the pipeline processing that facet isn't running anymore. Anyhow, if you kill all the processes (and maybe check if they are indeed killed) then Factor isn't running anymore. Which also means that it should be safe (well as safe as it's going to be) to re-start Factor.

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