You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we follow the Spectra package structure the accessor function rtime() and intensity() should give an ouput as a NumericList
I always will check in the validPeaksData() function that we have numeric data anyway so is it necessary ? NumericList are a bit less efficient.
just wondering if there is any reason to keep it that way and what would be the drawbacks to just have a list ?
Could a future ChromBackend implementation need this ?
The text was updated successfully, but these errors were encountered:
Some extra info: here are the results of a microbenchmark with and without having a NumericList as an output instead of normal list output.... It's not just a bit less efficient, this is pretty consequential.
I would go for a list of numeric for now. The backend needs to ensure that the list it returns is indeed a list of numeric (not some random logical or character in it), but that's something that the backend can check e.g. when initialized.
Worst case we can always wrap an additional NumericList() call around the returned list...
it is just important that we properly define and document the (expected) type of the return value of methods (this should go into the documentation of the ChromBackend.
Yes as of now I find it more easy to implement and it seems that it is just more efficient in general. Also I implement a .CORE_PEAKS_VARIABLES which defines the names and class of these, which makes it easy for me to check that they are indeed numeric.
If something comes up I'll add to the discussion :)
If we follow the Spectra package structure the accessor function
rtime()
andintensity()
should give an ouput as aNumericList
I always will check in the
validPeaksData()
function that we have numeric data anyway so is it necessary ?NumericList
are a bit less efficient.just wondering if there is any reason to keep it that way and what would be the drawbacks to just have a
list
?Could a future
ChromBackend
implementation need this ?The text was updated successfully, but these errors were encountered: