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

Reference frame for defining scattered angles with non-default incident direction #170

Open
GoogleCodeExporter opened this issue Aug 12, 2015 · 4 comments
Assignees
Labels
comp-UI Related to user interface (command line, input files) pri-Medium Worth assigning to a milestone usability Makes using code more convenient
Milestone

Comments

@GoogleCodeExporter
Copy link

Currently, we are working on DDA near surface, in which the laboratory 
reference frame (RF) will have larger emphasis, since it will be linked to the 
orientation of the surface. Therefore, we plan to define the scattering angles 
with respect to the laboratory RF, irrespective of the propagation direction 
(by the way, the default propagation direction is expected to be different too, 
along the _negative_ z-axis).

So, first, there will be different definitions of scattering angles for 
standard and near-surface modes. The idea of this issue is to merge them, i.e. 
to make the standard definition also with respect to the laboratory reference 
frame. However, there may be a lot of consequences of such changes (including, 
calculations of scat_grid and alldir), so a careful consideration is required. 
This may be connected to (simplified by) issue 138.

Original issue reported on code.google.com by yurkin on 6 Aug 2013 at 8:37

@GoogleCodeExporter
Copy link
Author

Original comment by yurkin on 9 Aug 2013 at 12:28

  • Added labels: Milestone-1.4

@GoogleCodeExporter
Copy link
Author

r1255 provides a lot towards implementing this issue. Moreover, it was decided 
to keep the default incident direction along +z axis in all cases.

Original comment by yurkin on 20 Aug 2013 at 12:14

@GoogleCodeExporter GoogleCodeExporter added OpSys-All comp-UI Related to user interface (command line, input files) usability Makes using code more convenient pri-Medium Worth assigning to a milestone labels Aug 12, 2015
@myurkin myurkin modified the milestone: 1.4 Aug 13, 2015
@myurkin myurkin added feature Allows new functionality and removed Milestone-1.4 labels Aug 13, 2015
@myurkin
Copy link
Member

myurkin commented Aug 14, 2015

#138
r1255 - a334ba6

@myurkin
Copy link
Member

myurkin commented Aug 11, 2020

A small summary of the problem: Currently the specification of the scattering plane (in which the Mueller matrix is calculated and further saved to mueller) is controlled by two options (-yz and -scat_plane), which naming is not immediately straightforward. It corresponds to yz-plane in the beam reference frame and a plane in laboratory frame through incident direction and ez (xz-plane for default incidence). Moreover, these two options are exclusive, and if none is used the default behavior depends on -surf and -store_scat_grid (or -phi_integr).

So it makes sense to make a single option, e.g. -scat_plane with arguments to control this behavior. Moreover, as mentioned originally in this issue there is no (or very little) motivation to keep the scattering plane tied to the incident direction (as is now in free space). If we change that, there will actually be a difference between rotating a particle, or rotating a beam (since the scattering plane will be defined in the lab frame).

@myurkin myurkin removed the feature Allows new functionality label Apr 24, 2021
@myurkin myurkin modified the milestones: 1.5, 1.6 Apr 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
comp-UI Related to user interface (command line, input files) pri-Medium Worth assigning to a milestone usability Makes using code more convenient
Projects
None yet
Development

No branches or pull requests

2 participants