-
Notifications
You must be signed in to change notification settings - Fork 13
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
Number of rows inconsistent after removing auto-correlations #133
Comments
Yep, time to switch to master... oms-deploy has been merged, and this error has been fixed since then... |
Thanks, running again now. I'm getting this since switching back to master and rebuilding:
Does Montblanc also need rebuilding? Also, do you know why I might get
errors when my parset looks like this?
|
On the Montblanc front, that "error" is normal. I get it consistently. @sjperkins Would you like to comment on what it means? Regarding the saving error, I am not sure, but it might have to do with case sensitivity. Would you mind trying to label the section in lower case and then specify the option with lower case? Just to test this theory. The alternative is that something is going awry with the template. I would check the case thing first though. |
Tensorflow binary wheel are targeted at a reduced instruction set in order to be compatible with a wide range of CPUs. You can read more about this here. Tensorflow 1.6 wheels will be built with AVX instructions. In fact, this does not affect the Montblanc C++/CUDA tensorflow operators which are built from source on each install with ['-march=native', '-mtune=native'] |
It's still going a day later, just over half way... 😭 Just dawned on me that I should just average the MS and test drive the interpolation features. I'll try the dE/de thing when it's finished. |
I replaced everything that was dE with de in both parset and command line call, and now the save-to option is behaving now. |
I'm trying G+dE cal on some ASKAP data. Has anyone seen this error before? Note that direction-independent (phase-diag) calibration reading from just the MODEL_DATA column works fine.
The text was updated successfully, but these errors were encountered: