LoopStructural.modelling.core.geological_model ~ WARNING ~ No data for Darling, skipping[BUG]

[mustaeenqazi]

Hi,
I get the warning "No data for Darling(name of the formation) when i run:

model.create_and_add_foliation("Darling",
interpolatortype="PLI",
nelements=1e4,
buffer=0.3,
solver='pyamg',
damp=True
)

Darling is the formation for which i have the dip and azimuth.

The data i have is attached as a screenshot with this report.

LoopStructural/modelling/core/geological_model.py line 605 to 609 it gives the reason for warning,

add data

    series_data = self.data[self.data['feature_name'] == series_surface_data]
    if series_data.shape[0] == 0:
        logger.warning("No data for %s, skipping" % series_surface_data)
        return

which seems not the case with my data.

[Lachlan Grose]

Hi,

LoopStructural uses "feature_name" not "formation" to distinguish the different stratigraphic units, foliations and faults. Your dataframe shows the column formation - if you rename it to feature_name it should work.

Cheers,

Lachlan

[mustaeenqazi]

Thank you very much, Yes i figured this and changed the name of the column to "feature_name". This error is gone, but there is another error, while running the same code, somehow the interpolator is getting a "None_type object and cannot set the property name". The error message and the code which generates the error are attached hereby in this comment. Please have a look
![

[Lachlan Grose]

Hi,

The error "Cannot create interpolator: number of steps is too small" suggests that you need to increase the resolution of the model. LoopStructural uses cubic elements for interpolation so the x,y,z dimensions of the elements are equal. This means for areas with a large map extent and a thin model if a small number of elements are used the number of steps in z is automatically calculated to be too small. If you try increasing nelements this error should go away. Maybe nelements=5e4.

Good luck

[mustaeenqazi]

thank you very much for input, the bug for which I raised the issue originally, is solved so i will close the Issue, and describe the new bug in detail in next issue.