Read in complex 2dseq #14
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…there is now a new property reco_type which uses VisuCoreFrameType to determine if the reco was magnitude or real and imaginary. This will be upgraded to also read in in real or imaginray or phase or IR reconstructed data
…ion at the end of the array
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A new property
reco_typefor 2dseq files was created. This now checks the VisuCoreFrameType in the visu_pars file.Depending on the value (IMAGINARY_IMAGE + REAL_IMAGE, IMAGINARY_IMAGE, REAL_IMAGE, PHASE_IMAGE or MAGNITUDE_IMAGE (default)), in
deserializein theschemas.pyand loads the data accordingly.This means that complex reconstructed data (REAL_IMAGE AND IMAGINARY_IMAGE) will be loaded as complex data