Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

widget Shadow->Footprint can't connect to OE's #17

Open
wgrizolliALS opened this issue Dec 13, 2024 · 11 comments
Open

widget Shadow->Footprint can't connect to OE's #17

wgrizolliALS opened this issue Dec 13, 2024 · 11 comments

Comments

@wgrizolliALS
Copy link

When trying to connect "Shadow->Footprint Reader" to a SHADOW OE's, nothing happens.

Another way to reproduce is to try to open SN_17keV_PD_Mirrors_Mono.ows

which (according to slides) uses Footprint Reader. When opening the file on OASYS we get the errors

ValueError("'Footprint' is not a valid output channel name for 'Plane Mirror'.")
ValueError("'Footprint' is not a valid output channel name for 'Ellipsoid Mirror'.")
ValueError("'Footprint' is not a valid output channel name for 'Plane Crystal'.")
ValueError("'Footprint' is not a valid output channel name for 'Plane Mirror'.")
@wgrizolliALS
Copy link
Author

Slide for reference:

Source

image

@lucarebuffi
Copy link
Member

You must enable the footprint beam in the preferences.

Screenshot 2024-12-13 at 3 56 47 PM

@wgrizolliALS
Copy link
Author

The setting was correct.

Recording.2024-12-13.140223.mp4

@lucarebuffi
Copy link
Member

is the widget enabled to emit the footprint?

@wgrizolliALS
Copy link
Author

I can't find that setting. Can you be more specific?

@lucarebuffi
Copy link
Member

Screenshot 2024-12-13 at 4 09 30 PM

@lucarebuffi
Copy link
Member

In any case, you should be able to connect it if the footprint beam is enabled.
I can't reproduce your error, sorry.

@lucarebuffi
Copy link
Member

Screenshot 2024-12-13 at 4 12 52 PM

@wgrizolliALS
Copy link
Author

Screen.Recording.2024-12-13.141205.mp4

@lucarebuffi
Copy link
Member

Said that, why you didn't contact me directly?

@wgrizolliALS
Copy link
Author

Sure, not a problem :) . I thought this was the preferred way to keep the information public. I will reach out directly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants