-
Notifications
You must be signed in to change notification settings - Fork 21
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
GetBcyl Issue in FIELDLINES #141
Comments
@WillT22 From the source, the error probably indicates that a point isoutside the VMEC domain.
|
This might be also related to #142 and can be merged if so. |
@WillT22 Can you upload the VMEC wout file? I'd like to check this against the #142 issue as @zhucaoxiang suggests. |
@lazersos Here you go. Let me know if you need anything else. |
For the NR and the NZ parameters, I was using 201 divisions which is the number provided in the example on the VMECwiki. I have adjusted these values down to 180 and up to 220 individually and together in the FIELDLINES input file on a simulation that ran before this issue arose. All tests yielded the same error as shown above. |
@WillT22 Can you upload the input file (assume it's fixed boundary). I'd like to run this case. Also please post your command for running FIELDLINES. I suspect what you're running into is an edge related issue which arrises for strongly cusped equilibria. The fix for the axis problem will most likely also provide improvements for the edge. Unfortunately, I'm busy with hardware from now till Christmas so I don't think I'll have much time to work on this. |
@lazerso Here is the input file and the .batch file I use to run in FIELDLINES modified for the fixed boundary condition whenever you can get to it. |
Sorry, took a while for me to get back to this. Here are the issues I see
|
When running previously successful simulations on FIELDLINES, I am now running into an initialization loop error. Attached is the error file when run on NoMachine. The error looks to be with GetBcyl specifically.
NX_error.txt
The text was updated successfully, but these errors were encountered: