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

Laser tab clarifications/updates #6005

Open
2 tasks
gurhar1133 opened this issue Jun 22, 2023 · 2 comments
Open
2 tasks

Laser tab clarifications/updates #6005

gurhar1133 opened this issue Jun 22, 2023 · 2 comments
Milestone

Comments

@gurhar1133
Copy link
Contributor

  • Number of mesh points “in slice” is confusing
  • Change how we initialize from function? Place all slices at the same z?
    • Then on plots need to indicate the time of the slice relative to t_0, something like +-40ps

@k-wolfinger I think wee need some more context for these Laser tab update requests

@gurhar1133 gurhar1133 added this to the silas milestone Jun 22, 2023
@k-wolfinger
Copy link
Member

k-wolfinger commented Jun 22, 2023

The second item, about how we initialized the function and indicate the slice positions, is not yet implemented in rslaser.

Essentially, we currently give all the laser slices the same time values and different position values, relative to the center of the pulse. We want to change that so that they all have the same position value and different time values, relative to the center of the pulse.

So, instead of plotting longitudinally vs z, we would plot longitudinally vs t. And that t would be the time for that slice to propagate to the center of the pulse (values around +40ps or -40 ps).

I hope that helps for that point?

@k-wolfinger
Copy link
Member

For the first item, I think the confusion would be cleared up if we wrote something like "Number of Grid Cells in Transverse Slice" and for the two boxes: "Horizontal (x)", "Vertical (y)".

This is not a personal point of confusion, so I am not certain what will clear it up, but changes like these will help.

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