You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We aim to supply custom beams to the fit_element app. For this purpose, we want to create custom CST files. Do you have an example CST file with some documentation? We know that the cst file requires a specific format based on amplitude and phases in theta and phi coordinates. We have an electromagnetic antenna beam patterns in the farfield approximation (XY). What is the convection you use for defining theta-phi coordinates for cst file? @rohitcbscient
The text was updated successfully, but these errors were encountered:
Hi, sorry for the delay in getting back to you - somehow I missed this. You may not get good results using the fit_element_data app (the fitting can get stuck with complex patterns). However, if you want to give it a try, the convention is that theta is the polar angle measured from the zenith to the horizon, and phi is the azimuthal angle in the horizon plane measured from East towards North.
@fdulwich Thanks for the reply. :-) We essentially want to use other beam patterns. Is there a way to create binary files with our spline fit coefficients if the fits are not accurate? In this case, we can do a spline fit externally and write out the coefficient into the oskar binary file, which can be understood by the interferometry module.
We aim to supply custom beams to the fit_element app. For this purpose, we want to create custom CST files. Do you have an example CST file with some documentation? We know that the cst file requires a specific format based on amplitude and phases in theta and phi coordinates. We have an electromagnetic antenna beam patterns in the farfield approximation (XY). What is the convection you use for defining theta-phi coordinates for cst file?
@rohitcbscient
The text was updated successfully, but these errors were encountered: