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

Import custom beams into fit_element / format of the cst files #42

Open
cvoegele opened this issue Jul 8, 2022 · 2 comments
Open

Import custom beams into fit_element / format of the cst files #42

cvoegele opened this issue Jul 8, 2022 · 2 comments

Comments

@cvoegele
Copy link

cvoegele commented Jul 8, 2022

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

@fdulwich
Copy link
Contributor

fdulwich commented Aug 8, 2022

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.

@rohitcbscient
Copy link

@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.

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

3 participants