IPKM/nmreval
15
2
Fork 1
Code Issues 41 Pull Requests Actions Packages Projects Releases Wiki Activity

[Feature]: Read in spectra with imaginary part from grace #273

New Issue
Closed
opened 2024-06-11 09:26:23 +00:00 by saeckech · 1 comment
saeckech commented 2024-06-11 09:26:23 +00:00
Member
Copy Link

Proposed Behavior

When reading in a spectrum (real + imag) from grace, the connection between real and imaginary part is lost. Phase correction or backwards fourier transformations are unavailable.
Ideally the real and imag parts would be (automatically) assigned on read-in.

Possible benefits

No response

Anything else?

No response

### Proposed Behavior When reading in a spectrum (real + imag) from grace, the connection between real and imaginary part is lost. Phase correction or backwards fourier transformations are unavailable. Ideally the real and imag parts would be (automatically) assigned on read-in. ### Possible benefits _No response_ ### Anything else? _No response_
saeckech added the
Kind/Feature
Kind/Enhancement
 labels 2024-06-11 09:26:23 +00:00
dominik self-assigned this 2024-06-12 16:33:27 +00:00
dominik added the
Reviewed/Won't Fix
 label 2024-06-12 16:34:05 +00:00
dominik commented 2024-06-12 16:42:07 +00:00
Member
Copy Link

Das lässt sich nach dem Einlesen über Data / Change datatypes.

  • Merge to complex set auswählen,
  • mit Drag & Drop die Datensätze in die rechte Liste schieben,
  • entsprechenden Datentyp auswählen.
    Das sollte einen neuen Datensatz erzeugen mit Real-/Imaginärteil.

Das aus der Grace-Datei automatisch auszulesen ist unmöglich. Und im Dialogfenster sehe ich da auch keine wirklich schöne Möglichkeit, diese Auswahl zu treffen.

Das lässt sich nach dem Einlesen über _Data / Change datatypes_. + _Merge to complex set_ auswählen, + mit Drag & Drop die Datensätze in die rechte Liste schieben, + entsprechenden Datentyp auswählen. Das sollte einen neuen Datensatz erzeugen mit Real-/Imaginärteil. Das aus der Grace-Datei automatisch auszulesen ist unmöglich. Und im Dialogfenster sehe ich da auch keine wirklich schöne Möglichkeit, diese Auswahl zu treffen.
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/Enhancement
Kind/Feature
Reviewed/Won't Fix
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
aahmad anisar ckolb cwolter dominik dwuerz elisa fwolter huczhang kschroeder malbrecht mandal markusro mbergmann mhaneke robin saeckech skloth skrueger
No Assignees dominik
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: IPKM/nmreval#273
No description provided.
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?