Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • L LAMP
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 12
    • Issues 12
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Scientific Software
  • LAMP
  • Issues
  • #33
Closed
Open
Issue created Jul 30, 2019 by Miguel Angel Gonzalez@gonzalezmOwner

Check reading of old data and add unit tests for each file version

Reported by Mark Telling (ISIS) on July 30th 2019, who could not reanalyse old IN16 elastic scans. Checking the problem I found that at some point I had messed up in rdid.pro, so this case (elastic scan with the PSD detector) was not handled correctly. It seems this has been there for a long time (probably since 2014), but apparently not discovered before (or not reported). I am going to implement a quick solution for Mark's case, but ideally, reading of all old data should be checked and introduced as unit tests. I will try to start with IN16 and Salsa, and then continue with other instruments.

Assignee
Assign to
Time tracking