fix: added thickness calculator fields

[AngRodrigues]

• also adds back the linting actions to ci

[lachlangrose]

Looks good, my only comment is this breaks how LS reads the projectfile for stratigraphic thicknessses. I can make some changes to LS to make this work but I think there needs to be a variable in the projectfile to indicate which thickness is to be used. Maybe in the thicknessCalculator element there could be a boolean flag to say whether it is active or not, although we need to make sure only one is active!

[AngRodrigues]

Looks good, my only comment is this breaks how LS reads the projectfile for stratigraphic thicknessses. I can make some changes to LS to make this work but I think there needs to be a variable in the projectfile to indicate which thickness is to be used. Maybe in the thicknessCalculator element there could be a boolean flag to say whether it is active or not, although we need to make sure only one is active!

Yeah, I can understand that. This would come from map2loop.
Thinking about implementing this,

• How about the user can define this flag with something like proj.set_loopstructural_thickness(InterpolatedStructure),
• or if not defined, flag the first calculator in the list.

@lachlangrose Would you agree with this?

[lachlangrose]

yeah sounds perfect. I would call the function set_active_thickness and the default active thickness is the label of the first thickness calculator in the list.