IPKM/nmreval
16
2
Fork 1
Code Issues 43 Pull Requests Actions Packages Releases Wiki Activity

Scale, shift #321

New Issue
Closed
opened 2026-04-15 11:53:20 +00:00 by skrueger · 0 comments
skrueger commented 2026-04-15 11:53:20 +00:00
Member
Copy Link
Copy Source

Current behavior

Beim speichern von gescaled oder geshifteten Daten steht im header Folgendes:

shift: [1, 0.00021544346900318487]

scale: [0, 0]

allerdings habe ich meine Daten um den angegebenen Faktor gescaled und nicht geshiftet. Ich denke das wird einfach falschherum gespeichert, dh Folgendes wäre richtig:

scale: [1, 0.00021544346900318487]

shift: [0, 0]

Version

2026-01-30

Expected behavior

No response

Steps to reproduce

No response

Log messages

No response

Anything else?

No response

### Current behavior Beim speichern von gescaled oder geshifteten Daten steht im header Folgendes: # shift: [1, 0.00021544346900318487] # scale: [0, 0] allerdings habe ich meine Daten um den angegebenen Faktor gescaled und nicht geshiftet. Ich denke das wird einfach falschherum gespeichert, dh Folgendes wäre richtig: # scale: [1, 0.00021544346900318487] # shift: [0, 0] ### Version 2026-01-30 ### Expected behavior _No response_ ### Steps to reproduce _No response_ ### Log messages _No response_ ### Anything else? _No response_
skrueger added the Kind/Bug label 2026-04-15 11:53:20 +00:00
dominik was assigned by skrueger 2026-04-15 11:53:20 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Kind/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Crash
This issue describes unexpected shutdowns or non-responsive behaviors
 Kind/Documentation
Improves documentation
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New feature
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Priority
Very low
The priority is very low
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid isssue
Reviewed/Won't Fix
This issue won't be fixed
Status
Need More Info
Feedback is required to reproduce issue or to continue work
Status
On Hold
This issue or pull request is on hold
Status
Stale
Issues without activity for more than 6 months
Type/BDS
Issues connected to BDS
 Type/DSC
Issues connected to DSC
 Type/Fit
Issue is connected to fitting data
 Type/General
issue connected to general functionality
 Type/NMR
Issues connected to NMR
No Label Kind/Bug
Milestone
No items
No Milestone
Assignees
Clear assignees
aahmad (Arshid Ahmad) anisar (Aqsa Nisar) ckolb (Christian Kolb) cwolter (Celine Wolter) dominik (Dominik Demuth) dwuerz (David Würz) elisa (Elisa Steinruecken) fwolter (Finn Wolter) huczhang (Huanchen Zhang) jepsinrajkp (Jepsinraj Kakkuzhiyulla Parambath) kschroeder (Katharina Schroeder) malbrecht (Maximilian Albrecht) mandal (Suvendu Mandal) markusro (Markus Rosenstihl) mbergmann (Mark Bergmann) mhaneke (Markus Haneke) robin (Robin Horstmann) saeckech (Christoph Säckel) skloth (Sebastian Kloth) skrueger (Sandra Krüger) ypiliauskaya (Yauheniya Piliauskaya)
No Assignees dominik
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: IPKM/nmreval#321
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?