-
Notifications
You must be signed in to change notification settings - Fork 30
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
Don't call fs_read_and_perturb for bool array #136
Comments
@phmarti As you said, it doesn't make sense to perturb a boolean array. I think your solution is fine. By the way, what is done for integer at the moment? I think it also doesn't make so much sense to perturb it ... |
👍 |
integer also simply call fs_read_int |
PR #138 How do you test the fs_read_and_perturb calls? |
@phmarti So far looks like it's not tested |
I would like to keep this issue open as we are introducing again code in the serialbox core which is driven by an application (pp_ser) just because it is not smart enough to use the library properly... |
Ok ... make sense |
pp_ser.py generates the fortran calls for write, read and read & perturb but fs_read_and_perturb is not implemented for bool arrays.
It clearly doesn't really make sense to perturb the boolean masks, but in the current state trying to serialize a bool array generates non compilable code (even if only write or read is used).
I suspect pp_ser.py doesn't know about data types, right? Couldn't fs_read_and_perturb_bool simply call fs_read_bool?
The text was updated successfully, but these errors were encountered: