Hello, thanks for your interest.
We choose to use json format because it provides a human-friendly format suitable for encapsulating all the information for defining the ground motion in a single file.
It is a simple text file, you can edit using any text editor.
Let me use this example to explain:
https://nheri-simcenter.github.io/s3hark-Documentation/_downloads/3998362659b66102f79aa5f88ada16e0/SRT-GM-Input-Style3-full.jsonIf you open it, you'll see its structure like shown in the attached figure.
You only need to change a few things to fit for your data:
1. You can see the type of this motion is "UniformVelocity", which means in the "data" section, you should input velocity values.
2. "numSteps" = 7998, it means there should be 7889 values in the "data" section.
3. In the units section, you only need to change the 'length' unit to either "in" or "m", means inch or meter. So the unit of the "data" is in/sec or m/sec, depending on the 'length' unit you choose
4. "dT" means the interval between the "data" values, dT's unit in this example is second, because you "time":"sec"
To account for the finite rigidity of the underlying half-space (bed rock), a Lysmer-Kuhlemeyer (1969) dashpot is incorporated at the base of the soil column.
Let me know if I answered your question.