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

Default number of wcycles and pcycles is 0 #106

Closed
kslong opened this issue Sep 3, 2014 · 3 comments
Closed

Default number of wcycles and pcycles is 0 #106

kslong opened this issue Sep 3, 2014 · 3 comments
Assignees

Comments

@kslong
Copy link
Collaborator

kslong commented Sep 3, 2014

At present, if you start python on a blank file and just hit carriage return for every variable you will find the program does not run very far and the pf file will not be created because the ionization and spectral cycles will be set to zero. We would like be able to create a vanilla pf file, that does run quickly, but it should run.

Investigating the problem shows that there is currently a hard to understand interaction between the variables wcycle, wcycles, ..., which are used only in the main program and the corresponding veraibles geo.wcycle, geo.wcycles, ...

One could fix things so that the default changed, with some kind of if statement near where data were read from the command line, but this is probably just a band aid a better approach is probably to remove just use the geo variables everywhere and delete the variables wcycle, wcycles, etc from the main routine.

The concern is that there might some failure situations involving things like restarts that would be a problem.

@kslong kslong self-assigned this Sep 3, 2014
@kslong kslong added this to the Public Release milestone Sep 3, 2014
@kslong
Copy link
Collaborator Author

kslong commented Sep 3, 2014

I've now committed a change to dev that fixes this problem, and eliminates the variables that were in main in favor of using the same variables in geo. I could not find anything that looked like it was a problem associated with anything like restarts or multiprocessor issues. Others should check however.

@kslong
Copy link
Collaborator Author

kslong commented Sep 3, 2014

... what I meant was committed and pushed to the dev branch.

@jhmatthews
Copy link
Collaborator

Commit here: agnwinds/python@0a0fc57

Looks good Knox. I also like the addition of Log_debug.

The wcycles/pcycles thing reminds me that there may be something similar happening with NPHOT and photons_per_cycle. I'll try and remember to take a look at this.

EDIT: I did and this was done in #115

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