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

Asymmetric TOD laser has unwanted initialisation behaviour #4869

Open
JessicaTiebel opened this issue Apr 10, 2024 · 1 comment
Open

Asymmetric TOD laser has unwanted initialisation behaviour #4869

JessicaTiebel opened this issue Apr 10, 2024 · 1 comment
Assignees
Labels
component: core in PIConGPU (core application) component: user input signals changes in user API such as .param files, .cfg syntax, etc. - changelog! feature request a request or suggestion to implement new functionality good first issue signal new contributors where they can start
Milestone

Comments

@JessicaTiebel
Copy link
Contributor

I wanted to use a laser with third order dispersion, which should and does produce an asymmetric laser in the longitudinal direction. But using the DispersivePulse incidentField profile the maximum of the pulse is set to be in the centre of the initialisation time. Due to the asymmetry of the laser and the periodicity of the FT used to calculate the laser profile, an edge is formed in the envelope. In the attached picture you can see what I mean.

As an example a simulation with:

  • TOD: 4500 $\mathrm{fs}^3$
  • GDD: 350 $\mathrm{fs}^2$
  • PULSE_DURATION_SI: 30.0e-15 / 2.354820045
  • PULSE_INIT: 20
  • $\Delta t $: 1.39e-16 * 0.523427 s

issue_TOD

@steindev steindev added component: core in PIConGPU (core application) component: user input signals changes in user API such as .param files, .cfg syntax, etc. - changelog! good first issue signal new contributors where they can start feature request a request or suggestion to implement new functionality labels Apr 26, 2024
@steindev steindev added this to the Future milestone Apr 26, 2024
@steindev
Copy link
Member

So what you are asking for is a parameter to shift the maximum away from the center of the initialization time interval?

That is easy to implement, as the parameter in principle already exists. One just needs to add an extra shift and expose this extra shift as a parameter of the laser profile. Easy for you to do!

See (

float_X const timeDelay = mue + focusPos / SPEED_OF_LIGHT;
)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: core in PIConGPU (core application) component: user input signals changes in user API such as .param files, .cfg syntax, etc. - changelog! feature request a request or suggestion to implement new functionality good first issue signal new contributors where they can start
Projects
None yet
Development

No branches or pull requests

2 participants