param study dat files #49

Closed
opened 2022-02-01 12:08:55 +01:00 by usov_i · 4 comments
usov_i commented 2022-02-01 12:08:55 +01:00 (Migrated from gitlab.psi.ch)

Created by: zaharko

Jakub reported that he cannot read multiple dat files with this local pyzebra, while I can do it
And I cannot plot any parameters after fitting the dat files neither with http://pyzebra.psi.ch:5006/ nor local pyzebra
20210093

*Created by: zaharko* Jakub reported that he cannot read multiple dat files with this local pyzebra, while I can do it And I cannot plot any parameters after fitting the dat files neither with http://pyzebra.psi.ch:5006/ nor local pyzebra <img width="1391" alt="20210093" src="https://user-images.githubusercontent.com/50512596/151957940-cd3fb190-7d4a-4596-9df6-7ca74b4e09d6.png">
usov_i commented 2022-02-01 17:31:01 +01:00 (Migrated from gitlab.psi.ch)

Created by: ivan-usov

This issue happens when fitting can't find appropriate parameter values, thus not being able to estimate std_err. Since we print the results in "Export file preview", and use std_err as error bars in 'parameter plot', it causes the error you mentioned.

What I could do for the time being is to assign std_err to 0 for those cases, which is not really correct, but at least will allow to browse the results and refine the fitting initial values/ranges. Alternatively, I can remove such scans from the "Export file preview" and also ignore them in 'parameter plot'. What would be a better option for you?

*Created by: ivan-usov* This issue happens when fitting can't find appropriate parameter values, thus not being able to estimate std_err. Since we print the results in "Export file preview", and use std_err as error bars in 'parameter plot', it causes the error you mentioned. What I could do for the time being is to assign std_err to 0 for those cases, which is not really correct, but at least will allow to browse the results and refine the fitting initial values/ranges. Alternatively, I can remove such scans from the "Export file preview" and also ignore them in 'parameter plot'. What would be a better option for you?
usov_i commented 2022-02-01 19:22:11 +01:00 (Migrated from gitlab.psi.ch)

Created by: zaharko

Dear Ivan,

Thank you for the today’s meeting!
Would it be an option to keep them in ‘export file preview’ and ignore them in ’parameter plot’?

Best wishes
Oksana

On 1 Feb 2022, at 17:32, Ivan Usov @.@.>> wrote:

This issue happens when fitting can't find appropriate parameter values, thus not being able to estimate std_err. Since we print the results in "Export file preview", and use std_err as error bars in 'parameter plot', it causes the error you mentioned.

What I could do for the time being is to assign std_err to 0 for those cases, which is not really correct, but at least will allow to browse the results and refine the fitting initial values/ranges. Alternatively, I can remove such scans from the "Export file preview" and also ignore them in 'parameter plot'. What would be a better option for you?


Reply to this email directly, view it on GitHubhttps://github.com/paulscherrerinstitute/pyzebra/issues/49#issuecomment-1027035820, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMBMFVDJZBGUFMSYJ5N44QDUZADJJANCNFSM5NI2JF3A.
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.
You are receiving this because you authored the thread.Message ID: @.***>

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

*Created by: zaharko* Dear Ivan, Thank you for the today’s meeting! Would it be an option to keep them in ‘export file preview’ and ignore them in ’parameter plot’? Best wishes Oksana On 1 Feb 2022, at 17:32, Ivan Usov ***@***.******@***.***>> wrote: This issue happens when fitting can't find appropriate parameter values, thus not being able to estimate std_err. Since we print the results in "Export file preview", and use std_err as error bars in 'parameter plot', it causes the error you mentioned. What I could do for the time being is to assign std_err to 0 for those cases, which is not really correct, but at least will allow to browse the results and refine the fitting initial values/ranges. Alternatively, I can remove such scans from the "Export file preview" and also ignore them in 'parameter plot'. What would be a better option for you? — Reply to this email directly, view it on GitHub<https://github.com/paulscherrerinstitute/pyzebra/issues/49#issuecomment-1027035820>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMBMFVDJZBGUFMSYJ5N44QDUZADJJANCNFSM5NI2JF3A>. 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>. You are receiving this because you authored the thread.Message ID: ***@***.***> [ { ***@***.***": "http://schema.org", ***@***.***": "EmailMessage", "potentialAction": { ***@***.***": "ViewAction", "target": "https://github.com/paulscherrerinstitute/pyzebra/issues/49#issuecomment-1027035820", "url": "https://github.com/paulscherrerinstitute/pyzebra/issues/49#issuecomment-1027035820", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { ***@***.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]
usov_i commented 2022-02-02 10:44:54 +01:00 (Migrated from gitlab.psi.ch)

Created by: ivan-usov

I pushed the changes to the test server. Could you try it and see if the fix is appropriate?

*Created by: ivan-usov* I pushed the changes to the test server. Could you try it and see if the fix is appropriate?
usov_i commented 2022-02-02 14:37:03 +01:00 (Migrated from gitlab.psi.ch)

Created by: zaharko

Hi Ivan,
Yes, it is very good this way.
Thank you!
Oksana

On 2 Feb 2022, at 10:45, Ivan Usov @.@.>> wrote:

I pushed the changes to the test server. Could you try it and see if the fix is appropriate?


Reply to this email directly, view it on GitHubhttps://github.com/paulscherrerinstitute/pyzebra/issues/49#issuecomment-1027754439, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMBMFVCOEN3MV7BHEMVHBLTUZD4KBANCNFSM5NI2JF3A.
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.
You are receiving this because you authored the thread.Message ID: @.***>

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

*Created by: zaharko* Hi Ivan, Yes, it is very good this way. Thank you! Oksana On 2 Feb 2022, at 10:45, Ivan Usov ***@***.******@***.***>> wrote: I pushed the changes to the test server. Could you try it and see if the fix is appropriate? — Reply to this email directly, view it on GitHub<https://github.com/paulscherrerinstitute/pyzebra/issues/49#issuecomment-1027754439>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMBMFVCOEN3MV7BHEMVHBLTUZD4KBANCNFSM5NI2JF3A>. 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>. You are receiving this because you authored the thread.Message ID: ***@***.***> [ { ***@***.***": "http://schema.org", ***@***.***": "EmailMessage", "potentialAction": { ***@***.***": "ViewAction", "target": "https://github.com/paulscherrerinstitute/pyzebra/issues/49#issuecomment-1027754439", "url": "https://github.com/paulscherrerinstitute/pyzebra/issues/49#issuecomment-1027754439", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { ***@***.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: zebra/pyzebra#49
No description provided.