Conversation
|
@joezuntz @marcpaterno I don't know if I am the only one having these problems with the new release. I added a simple python file here to show the problem if you have |
|
Thanks for this! It looks like the tests are failing because a data file is missing - does it need to call the create function first? We might actually want to use np.bool_ instead of just np.bool, that should also fix it. The error will depend on the numpy version used. |
By data file you mean the sacc file? if I just run this test with python I get: So it seems that it is generating the file normally but it is not able to read it. And if I add the lines for |
|
You can see the error message here: click the expand button next to the red marker |
I put this file in tests but the problem is not with pytest, I just putted it here to show the problem. To get the error I am talking about, just do |
☂️ Python Coverage
Overall Coverage
New FilesNo new covered files... Modified Files
|
|
The error doesn't appear when testing on Github actions. Could you tell me what version of numpy version you have so I can check against it? |
|
I have |
Thank you Joe. Sorry if it was me using it wrong somehow. |
|
No worries, this was a real issue! I'm just confused about why it shows up sometimes but not others! |
I see that there is a problem with the
load_fitsfunction and the new metadata reading from newer versions of sacc.When we generate the file, we create an empty metadata column. When running the
load_fitsmethod, it callsnumpy_to_vanillamethod to read all columns. If I am not wrong, recent updated made this function also read a metadata column. If there is nothing there, we go trough all the ifs:np.boolis deprecated and so it gives an error. I propose we removefrom the function. However IDK if there is other things to be checked since before there was no metadata column in the generated SACC files