-
Notifications
You must be signed in to change notification settings - Fork 127
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
Debug docs #225
base: master
Are you sure you want to change the base?
Debug docs #225
Conversation
Created debug page to be added to by others. I have put my brief thoughts in.
Added debug into index.
Extra embellishments
Good start, I've added just a little extra here and there. I guess there could be a good amount of discussion about what order we'd tend to prioritise the various steps listed. Worth remembering also that the column model isn't currently in the master. |
Mention the solution found in #80 |
----------------- | ||
A lot of issues on Isca can stem from parallelisation across multiple computing cores. If you run a job on 1 core and it works, you know that the problem lies here. Quite often it can be the allocation of the start/end integers ``is, ie, js, je`` | ||
|
||
Column Model |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd suggest removing the reference to the column model for now as it isn't in the master yet
----------- | ||
Be sure to output diagnostics that can help you diagnose the problem. That said, sometimes turning off diagnostics can stop model crashes. If this is the case, your problem is likely data related. | ||
|
||
Recompile |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps state this can be done by deleting the current isca_work
directory
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Were you still planning to include a comment relating to issue #80 ? I'm happy to approve in general just to get this in the docs if perhaps this is going to be added later.
I've created a page for debugging on here rather than the google doc.
Please add your comments, edit what's already been written and add more things. There is no right or wrong really, do not ask people to make changes, just make them yourself if you feel it is needed.
Thanks!