Some questions about the slip spatial database file

Dear Sir,
I have some questions about interpolation in spatial databases. In the crustal-strikeslip-3d example, the east_fault uses data-dim=1 for interpolation, while the main_fault and west_fault use data-dim=2. As I understand it, all of these are points on the fault surface, so they should use data-dim=2 for interpolation. What is the purpose of this configuration?

Another question is about how to create a reasonable spatial database file for slip distribution. Since my fault is dipping, how should I set up the slip file accordingly?

In addition, how should the slip distribution at different points be reasonably arranged?
In the example, there is a data point at the same depth beneath each known surface coordinate.
However, when I try to add a new point among them, I often encounter

[0]PETSC ERROR: Could not find values for initiation_time at.....

In fact, I added more data points, but similar errors still occurred.
Is interpolation related to the distribution of the data?
Should the data be distributed as evenly as possible, rather than having too many known values clustered at a single location?
Thanks!

The data-dim=1 is an error. Thanks for pointing this out!

How to layout the spatial database depends on what data you have and how it is organized. If you have data on a uniform grid, then keep the points for the spatial database on the grid and use the SimpleGridDB. If the grid of points is on a vertical plane, then keep the points in the same locations. If the grid of points is on a dipping plane, then keep them in the same location.

In general, for a dipping fault, you can point your points on a horizontal plane, vertical plane, or the 3D dipping plane. Just be aware that the points on the 3D dipping fault in PyLith will be projected onto the geometry of the spatial database for the interpolation. That is, the interpolation occurs in the geometry of the spatial database, not the geometry of the fault surface in the mesh you use in PyLith.

If you add points and the interpolation fails, then you might have incorrect information in the header. If you are using a SimpleDB and the points are clustered, then you can also run into this error.