PrometheusPi
commented
6 years ago In the input section of settings.hpp the data in the trajectory file is defined. By default a GPT output trajectory is assumed that looks like:
x_position[meter] y_position[meter] z_position[meter] beta_x[unitless] beta_y[unitless] beta_z[unitless] time[seconds] with beta being the velocity normalized to the speed of light and beta_{x,y,z} being its vector components.
Each column contains the value specified above. Each row contains a new point of the trajectory with an increased time.
This results in the following input settings:
namespace input
{
const unsigned int index_time = 6; /* column id of time */
const unsigned int index_pos_x = 0; /* column id of x */
const unsigned int index_pos_y = 1; /* column id of y */
const unsigned int index_pos_z = 2; /* column id of z */
const unsigned int index_beta_x = 3; /* column id of beta_x */
const unsigned int index_beta_y = 4; /* column id of beta_y */
const unsigned int index_beta_z = 5; /* column id of beta_z */
/* unit conversion to SI units */
const double convert_time = 1.0; /* s -> s */
const double convert_pos = 1.0; /* m -> m */
const double convert_beta = 1.0; /* None -> None */
}If you for example prefere cgs units and the trajectory you have is in units of
- time: seconds (s)
- position: centimeter (cm)
-
speed: cm/s with the above order, the input settings would looks like
namespace input { const unsigned int index_time = 0; /* column id of time */ const unsigned int index_pos_x = 1; /* column id of x */ const unsigned int index_pos_y = 2; /* column id of y */ const unsigned int index_pos_z = 3; /* column id of z */ const unsigned int index_beta_x = 4; /* column id of beta_x */ const unsigned int index_beta_y = 5; /* column id of beta_y */ const unsigned int index_beta_z = 6; /* column id of beta_z */ /* unit conversion to SI units */ const double convert_time = 1.0; /* s -> s */ const double convert_pos = 0.01; /* cm -> m */ const double convert_beta = 1.0/2.9978e10; /* cm/s -> None */ }
TheresaBruemmer
QJohn2017
This is a continuation of issue #93 Since the discussion changed from how to set up the environment on tianhe2 to how to set up Clara2 in general, I think a new issue should be used (to avid scrolling down through all the issues related to the module system on tinahe2)
This question was asked by @QJohn2017 in #93
In the beginning of
settings.hppyou find the basic parameters:0.01/s and go toomega_max1/stheta_max is the maximum opening angle of your detector in degree Setting the detector is not yet generic and requires some code adjustments we will discuss later
N_spectrum is the number of frequencies you want to sample between
0.01/s and go toomega_max1/sN_theta is the number of angle values between
0degree andtheta_maxdegree you want to sampleN_phi is the number of angles you want to sample orthogonally to theta
N_trace is the number of trajectories provided that you want to calculate the spectrum for.
fft_length_factor is a factor to increase the sampling of the trajectories via linear interpolation. This is essential when you undergo highly-nonlinear Thomson scattering for only a brief period of time compared to the entire duration of the trajectory (see https://doi.org/10.5281/zenodo.843510 section 4.1.3)
ascii_output if true returns the spectra as text file, if false returns the spectra as binary file
N_char_filename the number of characters that are needed to give the trajectory path.
256are usually sufficient, but if you have long directory names, more might be neededtraceFileTemplate the template for locating your input trajectories with [C-style])http://www.cplusplus.com/reference/cstdio/printf/) replacements
outputFileTemplate the template for the output spectra files with C-style replacements