bi-geometry
Export file contacts nan intensity in some well integrated peaks.
This changes from 'Function' to 'Area' intensity
In case of "Intensity: Function", the 'nan's in the output appear when fitting procedure can't estimate stderr for parameters.
Will output just the area, but its error will still be 'nan' in the "Export file preview:".
In case of "Intensity: Area", it happens because of repeated x values, so that scipy.simpson function has a division by zero, which results in 'nan'. A possible solution is average only some points upon merging.
Another option would be to rebin the data
*Created by: zaharko*
1. Ccl integrate
2. bi-geometry
Export file contacts nan intensity in some well integrated peaks.
This changes from 'Function' to 'Area' intensity
In case of "Intensity: Function", the 'nan's in the output appear when fitting procedure can't estimate stderr for parameters.
Will output just the area, but its error will still be 'nan' in the "Export file preview:".
In case of "Intensity: Area", it happens because of repeated x values, so that scipy.simpson function has a division by zero, which results in 'nan'. A possible solution is average only some points upon merging.
Another option would be to rebin the data
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Created by: zaharko
Export file contacts nan intensity in some well integrated peaks.
This changes from 'Function' to 'Area' intensity
In case of "Intensity: Function", the 'nan's in the output appear when fitting procedure can't estimate stderr for parameters.
Will output just the area, but its error will still be 'nan' in the "Export file preview:".
In case of "Intensity: Area", it happens because of repeated x values, so that scipy.simpson function has a division by zero, which results in 'nan'. A possible solution is average only some points upon merging.
Another option would be to rebin the data