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

progress reporting #26

Open
cbird808 opened this issue Aug 13, 2019 · 3 comments
Open

progress reporting #26

cbird808 opened this issue Aug 13, 2019 · 3 comments

Comments

@cbird808
Copy link
Contributor

now that the module load errors are fixed, it's much more difficult to figure out what is happening. It would be nice to be able to print more information to the screen. I noticed that the echos in the scripts go into the ether. is there a way to recover those?

@ekrell
Copy link
Contributor

ekrell commented Aug 14, 2019

Some content like the R scripts and various obitool errors make it through, but not echoes. I don't know why. I will set up a smaller test script and see what I can do.

@cbird808
Copy link
Contributor Author

Here is a hackish way to make the echos work:

@ekrell
Copy link
Contributor

ekrell commented Sep 12, 2019

I know why now. Whenever I call an SBATCH, I grep the output for only the job ID so that I can stall the next job until the job is done. But grepping means all the other STDOUT is gone. But STDERR makes it through.

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

2 participants