Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Graded beds in lithology track: PSICAT 1.2.0 #13

Open
jllancaster opened this issue Jul 18, 2024 · 1 comment
Open

Graded beds in lithology track: PSICAT 1.2.0 #13

jllancaster opened this issue Jul 18, 2024 · 1 comment

Comments

@jllancaster
Copy link

It appears that the feature allowing representation of a graded bed graphically in the lithology column by assigning different grain sizes to the top and bottom of the bed is now called the lithology (ANDRIL) column. The new CSD lithology column with grain size set in the grain size column does not appear to allow for representation of a graded bed. How does CSD represent graded beds with the new default lithology column? Similar to below?

image

@sorghumking
Copy link
Member

If you're looking for a way to draw an oblique line from a Lithology interval's top-right to base-right, there is no way to do so at present. I would recommend reverting to the legacy (Andrill) Lithology column in that case, but that comes with other caveats. The column persists in 1.2.0 primarily to preserve compatibility with older projects. We do not suggest using it for new projects.

Your pictured approach of using increasingly larger Grain Size intervals to increment the width of corresponding Lithology intervals certainly works, as long as you don't mind the "stepped" look!

That said, our intention for representing graded beds in 1.2.0 was to use the "Graded bedding, normal/reverse" options in the Bedding column. Creating such a Bedding interval will not affect the visual appearance of corresponding Lithology intervals. If there is sufficient interest, we might consider going down that road, but inter-column interactions between two columns (Lithology and Grain Size) is already a bit complex: adding a third (and inevitably fourth, fifth...) column to that stew could present challenges both visually and computationally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants