search

amisr / amisrsynthdata

Module for generating synethetic AMISR data files
GNU General Public License v3.0
3 stars 2 forks source link

Benchmark and Performance consideration #14

Open peijin94 opened 1 month ago

peijin94 commented 1 month ago

There should be descriptions of how long a typical synthetic data run takes.

For performance consideration: parsing txt file to number into numpy is much more time-consuming than direct loading .np or .npz file Replacing beamcodes text file with h5 or npz can optimize the speed of beams_from_beam_codes

peijin94 commented 1 month ago

np.in1d has a deprecation error, better change to isin

ljlamarche commented 1 month ago

The function np.in1d has been replaced with np.isin, as suggested. (37193986f4b24712f93c573c1098478c1937a149)

The beamcode *.txt files have been converted into a single h5 file. (c4bd66d38cee3b74519869ab819997e3c1ce989a)

ljlamarche commented 1 month ago

The time required for synthetic data to be created depends on the ionospheric state that is chosen and the resolution of the radar mode. A section on benchmarking has been added to the Usage section of the documentation. (45df529c81c3b91b6535e110674434cb8bbef74f)

Simple Complex
No Plots 0.77 s 87.48 s
Plots 9.72 s 103.24 s