Aakash Gupta
Aakash Gupta
I am trying to transform the axisem-generated databases for faster access for iterative inversion processes, as suggested by the developers. My axisem jobs are on our cluster, and I will...
While downloading data using PySEP, some steps of the procedure seem to be very slow, and if the flags requiring these steps are turned on, the data download can take...
While downloading data through PySEP, the process fails sometimes but eventually completes successfully on re-executing the job multiple times. It seems like the error has something to do with connecting...
There are different issues which show up when using the record section plotting tool for different sets of data - - no xticks are seen as such for the case...
In recsec, parameter `sort_by = “abs_azimuth”` brings in unwanted additional normalization to the seismograms. The zip file setup from [#156](https://github.com/adjtomo/pysep/issues/156) will still work. Run the script to generate a record...
It seems that `recsec` reads the `time shift` from `CMTSOLUTION` files and automatically applies that on synthetics. - For synthetic synthetic comparisons, this time shift does not seem to be...
In some cases the seismograms shown in a record section will need to be marked with vertical lines at multiple timestamps. One special case is where each seismogram will have...
The constructors of both classes - `Pysep` and `RecordSection`, offer a lot of flexibility through the innumerous parameters, both listed in the definition and hidden. The documentation does a good...
In order to scale seismograms so that they are visible on record sections, the parameter `scale_by = "normalize"` is used so that each seismogram's absolute amplitude is scaled to 1....
Parameter `time_shift_s` in `recsec` applies to both forms of data being compared. It can be a useful feature addition to also have the ability to move in time just one...