Skip to content
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.

Sign up for GitHub

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

Jump to bottom

SaveAscii spectra indexing #11364

Closed
raquelalvarezbanos opened this issue Nov 10, 2014 · 2 comments
Closed

SaveAscii spectra indexing #11364

raquelalvarezbanos opened this issue Nov 10, 2014 · 2 comments
Labels
Framework Issues and pull requests related to components in the Framework Low Priority Things that you don't ever want to be done. Stale This label is automatically applied to issues that are automatically closed by the stale bot

Comments

@raquelalvarezbanos
Copy link
Contributor

This issue was originally TRAC 10522

To reproduce:

Also:

Spectra ID should range from 1 to N instead of 0 to N-1.
@raquelalvarezbanos
Copy link
Contributor Author

@NickDraper (2015-04-27T08:10:35):
Moved to R3.5 at the R3.4 code freeze

@raquelalvarezbanos raquelalvarezbanos added Low Priority Things that you don't ever want to be done. Framework Issues and pull requests related to components in the Framework labels Jun 3, 2015
@raquelalvarezbanos raquelalvarezbanos added this to the Release 3.5 milestone Jun 3, 2015
@NickDraper NickDraper modified the milestones: Release 3.5, Release 3.6 Sep 14, 2015
@NickDraper NickDraper modified the milestones: Release 3.6, Release 3.7 Jan 22, 2016
@NickDraper NickDraper modified the milestones: Release 3.7, Release 3.8 May 20, 2016
@lottiegreenwood
Copy link

From testing it looks like the "Inconsistent spectra list" no longer appears when trying to save spectra n+1... but it also looks like no error message appears when you try to save a spectra number the dataset doesn't have - it just fails silently and doesn't produce a file. It still needs to be fixed to range from 1 to n instead of 0 to n-1

@lottiegreenwood lottiegreenwood removed their assignment Mar 28, 2017
@gemmaguest gemmaguest added the Stale This label is automatically applied to issues that are automatically closed by the stale bot label Jul 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Framework Issues and pull requests related to components in the Framework Low Priority Things that you don't ever want to be done. Stale This label is automatically applied to issues that are automatically closed by the stale bot
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@NickDraper @raquelalvarezbanos @lottiegreenwood @gemmaguest