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

[Feature]: add value to evaluate expression #202

New Issue
Closed
opened 2024-01-04 13:52:28 +00:00 by dominik · 3 comments
dominik commented 2024-01-04 13:52:28 +00:00
Member
Copy Link

Proposed Behavior

Access for each set to their respective numerical value via "value", similar to access to x and y.

Possible benefits

Possible examplary use case: Shift with given Arrhenius and use temperature as individual inputs.

Anything else?

No response

### Proposed Behavior Access for each set to their respective numerical value via "value", similar to access to x and y. ### Possible benefits Possible examplary use case: Shift with given Arrhenius and use temperature as individual inputs. ### Anything else? _No response_
dominik added the
Kind/Feature
Kind/Enhancement
 labels 2024-01-04 13:52:28 +00:00
dominik self-assigned this 2024-01-04 13:52:28 +00:00
saeckech commented 2024-01-04 13:55:25 +00:00
Member
Copy Link

value can already be accessed in evaluate expression via "value" (?)

value can already be accessed in evaluate expression via "value" (?)
dominik added the
Kind/Bug
 label 2024-01-04 14:01:34 +00:00
dominik commented 2024-01-04 14:01:59 +00:00
Author
Member
Copy Link

value can already be accessed in evaluate expression via "value" (?)

Na sowas, tatsächlich. Dann muss ich das ja nur oben in der Liste anzeigen lassen, damit unbedarfte Nutzer wie ich das auch wissen.

> value can already be accessed in evaluate expression via "value" (?) Na sowas, tatsächlich. Dann muss ich das ja nur oben in der Liste anzeigen lassen, damit unbedarfte Nutzer wie ich das auch wissen.
saeckech commented 2024-01-04 14:35:01 +00:00
Member
Copy Link

(however, "group" cannot yet be accessed this way I think)

(however, "group" cannot yet be accessed this way I think)
dominik added this to the (deleted) project 2024-01-19 10:22:46 +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
Kind/Enhancement
Kind/Feature
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#202
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?