jurra / rockin-webapp

A simple data entry webapp to enter rock sample data from wells drilled at TU Delft
MIT License
0 stars 0 forks source link

Core catcher related question #1

Closed jurra closed 11 months ago

jurra commented 1 year ago

Hi Liliana,

Another core catcher related question.

What happens if a person adds core_section a, and then core_section b. And then the person wants to add a core catcher for core a? Say we are starting to count from zero.

a =1 b =2 Then core catcher related to section_name one would end with 3?

For example: a = WELLNAME-C1-1 (core) b= WELLNAME-C1-2 (core) b = WELLNAME-C1-1-CC3 ? (core_catcher) d = WELLNAME-C1-4 (core)

Do you have an idea of how to go about this scenario or similar ones?

anailil commented 1 year ago

Hi Jose, the example you mention is never going to happen because the core catcher is a unique sample for each core and it only occurs at the very end of the whole core. Let me give you an example.: Core 1 (C1) has a total length of 59 m. It consists of 59 sections and one core catcher. Each section is of 1 meter length, also the core catcher is 1m length. Section numbers are sequential and the core catcher must be assigned the very last section. Like this:

On Wed, 28 Jun 2023 at 23:15, Jose Urra @.***> wrote:

Hi Liliana,

Another core catcher related question.

What happens if a person adds core_section a, and then core_section b. And then the person wants to add a core catcher for core a? Say we are starting to count from zero.

a =1 b =2 Then core catcher related to section_name one would end with 3?

For example: a = WELLNAME-C1-1 (core) b= WELLNAME-C1-2 (core) b = WELLNAME-C1-1-CC3 ? (core_catcher) d = WELLNAME-C1-4 (core)

Do you have an idea of how to go about this scenario or similar ones?

— Reply to this email directly, view it on GitHub https://github.com/jurra/rockin-webapp/issues/1, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE6ACV3HT6RE2J7GDHUYQODXNSNIPANCNFSM6AAAAAAZXVLFMY . You are receiving this because you were assigned.Message ID: @.***>