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
Currently, there are only two routines available for obtaining the far fields:
get_farfield: returns the far field at a single point
output_farfields: writes the far fields in a given Volume to an HDF5 file
It would be useful to have an additional third routine which returns the far fields in a given Volume as a NumPy array. This would facilitate post processing directly from within a single Python script without having to write and read from disk.
As an extension of this feature, rather than restrict the far field output to a rectilinear Volume, the region could be generalized to a GeometricObject (e.g., Sphere, Prism, Cylinder, etc.)
The text was updated successfully, but these errors were encountered:
Looks straightforward, because the dft_near2far::save_farfields function already collects all the necessary information in an array before writing it to disk. So we would want to:
Refactor save_farfields into two routines — a get_farfields_array that collects the EH array and a save_farfields that calls get_farfields_array and then saves it to HDF5.
Change get_farfields_array to use sum_to_all instead of sum_to_master so that all processes get the data.
Make a high-level wrapper around get_farfields_array and call it from Python.
Currently, there are only two routines available for obtaining the far fields:
get_farfield
: returns the far field at a single pointoutput_farfields
: writes the far fields in a givenVolume
to an HDF5 fileIt would be useful to have an additional third routine which returns the far fields in a given
Volume
as a NumPy array. This would facilitate post processing directly from within a single Python script without having to write and read from disk.As an extension of this feature, rather than restrict the far field output to a rectilinear
Volume
, the region could be generalized to aGeometricObject
(e.g.,Sphere
,Prism
,Cylinder
, etc.)The text was updated successfully, but these errors were encountered: