TRestRawSignalChannelActivityProcess. Moving fReadout after data members #81
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.
There was a problem retrieving the metadata members of the process
TRestRawSignalChannelActivityProcess
. I found out that moving thefReadout
pointer after the data members solves the problem.I used the following RML definition for testing.
The values before the fix were not correct, as shown here.
After moving the
fReadout
pointer one gets the right values.I am not sure why this problem is happening, I remember it happened before and we discussed a bit about it. But why the
fSignalEvent
pointer is not causing problem andfReadout
it is? It would be good to understand the cause so that we can add a validation pipeline to prevent this behaviour. Probably @nkx knows the reason of this.