-
Notifications
You must be signed in to change notification settings - Fork 10
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
FCI geometry: basic test #228
Conversation
Make it a bit easier to change the shape consistently for FCI. Also include guards.
Is that expected? Any hints what I need to change to fix it? |
Codecov Report
@@ Coverage Diff @@
## fci-geometry #228 +/- ##
================================================
+ Coverage 75.31% 75.86% +0.55%
================================================
Files 15 15
Lines 2702 2702
Branches 631 631
================================================
+ Hits 2035 2050 +15
+ Misses 435 420 -15
Partials 232 232
Continue to review full report at Codecov.
|
@dschwoerer the PR looks good to me. Error seems a bit odd - can you post a back-trace please? I can't see where the exception is coming from, doesn't seem to actually be in xBOUT... |
Ah, actually I think I might know what the problem was. xBOUT/xbout/plotting/plotfuncs.py Line 79 in e1b1e1c
was written to make 'poloidal plane' plots, assuming that the dimensions would be bout_xdim and bout_ydim . Actually plot2d_wrapper is most useful for that case, because it's only when we have an x-y plane that we might need to split up into different regions to plot. The best fix for this error might actually be to fix #167, so we can turn of poloidal_plot (which should get rid of the error), and check that when poloidal_plot=True the dimensions are actually bout_xdim and bout_ydim .
A workaround, since FCI doesn't use regions, is to just not use the xBOUT method, and instead do something like
|
...merging this on the assumption that my previous comment was the cause of the error @dschwoerer reported. We can fix that issue in a future PR. |
The test is failing, but with a slighly different error ... but I think this is related to dask ...