param study 2 issues #45

New Issue

Closed

opened 2021-11-08 13:39:34 +01:00 by usov_i · 2 comments

usov_i commented 2021-11-08 13:39:34 +01:00 (Migrated from gitlab.psi.ch)

Copy Link

Created by: zaharko

param study

• 1. merges files with different values of parameter (Temp in the attached case, files 7493-7515) and sets export to false
  
• 2. When four more scans are added (files 7519-7522) overview and overview map are not produced

*Created by: zaharko* param study - [x] 1. merges files with different values of parameter (Temp in the attached case, files 7493-7515) and sets export to false  - [x] 2. When four more scans are added (files 7519-7522) overview and overview map are not produced

usov_i commented 2021-11-08 18:05:45 +01:00 (Migrated from gitlab.psi.ch)

Copy Link

Created by: ivan-usov

The first issue is a direct consequence of https://github.com/paulscherrerinstitute/pyzebra/issues/37. Currently, there is no condition on the parameter when deciding which scans should be merged, and generally the parameter is unknown on that step, because can also be entered later manually by a user. I don't have in mind a better solution than adding "Restore scan" and "Merge into current" buttons, similar to ccl_integrate panel.

*Created by: ivan-usov* The first issue is a direct consequence of https://github.com/paulscherrerinstitute/pyzebra/issues/37. Currently, there is no condition on the parameter when deciding which scans should be merged, and generally the parameter is unknown on that step, because can also be entered later manually by a user. I don't have in mind a better solution than adding "Restore scan" and "Merge into current" buttons, similar to ccl_integrate panel.

usov_i commented 2021-11-08 19:30:07 +01:00 (Migrated from gitlab.psi.ch)

Copy Link

Created by: zaharko

Hi Ivan,
Yes, this is a good idea to add "Restore scan" and "Merge into current” buttons
Oksana

On 8 Nov 2021, at 18:05, Ivan Usov @.@.>> wrote:

The first issue is a direct consequence of #37https://github.com/paulscherrerinstitute/pyzebra/issues/37. Currently, there is no condition on the parameter when deciding which scans should be merged, and generally the parameter is unknown on that step, because can also be entered later manually by a user. I don't have in mind a better solution than adding "Restore scan" and "Merge into current" buttons, similar to ccl_integrate panel.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/paulscherrerinstitute/pyzebra/issues/45#issuecomment-963371211, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMBMFVA57M6OXLKF23CNXLLUK77PJANCNFSM5HSSCCXQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[ { @.": "http://schema.org", @.": "EmailMessage", "potentialAction": { @.": "ViewAction", "target": "https://github.com/paulscherrerinstitute/pyzebra/issues/45#issuecomment-963371211", "url": "https://github.com/paulscherrerinstitute/pyzebra/issues/45#issuecomment-963371211", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { @.": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

*Created by: zaharko* Hi Ivan, Yes, this is a good idea to add "Restore scan" and "Merge into current” buttons Oksana On 8 Nov 2021, at 18:05, Ivan Usov ***@***.******@***.***>> wrote: The first issue is a direct consequence of #37<https://github.com/paulscherrerinstitute/pyzebra/issues/37>. Currently, there is no condition on the parameter when deciding which scans should be merged, and generally the parameter is unknown on that step, because can also be entered later manually by a user. I don't have in mind a better solution than adding "Restore scan" and "Merge into current" buttons, similar to ccl_integrate panel. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<https://github.com/paulscherrerinstitute/pyzebra/issues/45#issuecomment-963371211>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMBMFVA57M6OXLKF23CNXLLUK77PJANCNFSM5HSSCCXQ>. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. [ { ***@***.***": "http://schema.org", ***@***.***": "EmailMessage", "potentialAction": { ***@***.***": "ViewAction", "target": "https://github.com/paulscherrerinstitute/pyzebra/issues/45#issuecomment-963371211", "url": "https://github.com/paulscherrerinstitute/pyzebra/issues/45#issuecomment-963371211", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { ***@***.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

0.7.11

0.7.10

0.7.9

0.7.8

0.7.7

0.7.6

0.7.5

0.7.4

0.7.3

0.7.2

0.7.1

0.7.0

0.6.5

0.6.4

0.6.3

0.6.2

0.6.1

0.6.0

0.5.2

0.5.1

0.5.0

0.4.0

0.3.2

0.3.1

0.3.0

0.2.2

0.2.1

0.2.0

0.1.3

0.1.2

0.1.1

0.1.0

Labels

Clear labels

bug

documentation

duplicate

enhancement

good first issue

help wanted

invalid

question

wontfix

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

sibille_r usov_i zaharko

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: zebra/pyzebra#45

No description provided.