Skip to content

Are scattered thrust uplifts possible? #13

@jennawest

Description

@jennawest

I am working on modeling the landscape of Wyoming during the Laramide orogeny which was a period where scattered basement-cored thrust uplifts occurred. I am looking for a way to make each block uplift by thrusting so a foreland basin is formed on the thrust side of each unit. A map of what my uplifts need to look like is in the attached folder, the file is called "Dickinson et al, 1988 map"

If I use *.UNIT files with no faults, just blocks set to a certain elevation, I do not get the foreland basins on a particular side of the unit (nofault.ps). But when I add thrust faults on one side of each unit I get a "hole" on the back of the unit where the unit started and has moved away from. I know TISC uses a mass balance approach so if you want to add a thrust block to the model, the back of the thrust has a hole where the sediments have moved out of to create uplift on the front of the thrust. To get around this you extend the block outside of the model domain so the hole is not visible (like in your demo 6_deformation). I was wondering if it is possible to get around this because the distribution of my uplifts means that the backs of the thrusts cannot be outside of the model domain. I have been working with the idea that maybe I can have each of the units move at different time periods so I can extend them outside of the model domain without interfering with each other but I have yet to be successful with this approach. I apologize that what I'm sending you is such a mess. I know that a way to get around this is to split the study area into smaller sections but I am trying to avoid that because it doesn't match the original project goals. Also, do you know why there are foreland basins on either side of the thrust belt even though it's moving in one preferential direction? It would seem it goes against the classic foreland basin model that has a foredeep on one side of the thrust.
60ma_thrust.zip

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions