crava / cravagui Goto Github PK

The uncertainty for the lowest zone will be ignored, but this is not very intuitive in the GUI. The user will only notice when reading the tool-tip. This should be done more intuitive, e.g., by disabling the input box for the uncertainty.

When opening a previous project the "Local noise" button appeares ticked when it's not supposed to (the xml-tree has the correct value, though.)

If the Local Noise button is ticked, the "Estimate Local Noise" button needs to be unticked and ticked for the change to take effect.

With given setup (file provided in separate email), the GUI crashes when switching from Multizone to Single Zone in the Horizons tab.

In the Multizone background model there will not be a default "Correlation structure" for the bottom zone (The radio button has chosen Top, but there is no value in the xml-tree).

Some settings are not written to xml-file. The behaviour is irregular, and needs to be investigated further.

In the Horizons tab:

1. Choose Multizone Inversion
2. Tick box "Use constant time value for top surface
3. Choose Single zone Inversion
4. Go back to Multizone Inversion

The box "Use constant time value for top surface" will be ticked, but no option for inputting a value.

In forward modeling mode: If you click "Delete stack" twice very fast on the last two stacks, the program will crash.

When choosing "Base correlation structure." for zone 1, and saving, and reopening the project, the choice is forgotten and one of the other correlation structures are shown. This only affects the first zone.

The tooltip for "Length of wavelet to be estimated" is very long, there should probably be a break in the text.

In estimation mode: The tags <vp-vs-ratio-from-wells> and <vp-vs-ratio> should be possible to control under "Setting". The tags are available in prediction mode.

Previously we had:

<wavelet-estimation-interval>
<top-surface-file> surface.txt </top-surface-file>
</wavelet-estimation-interval>

With the support of constant time surfaces, this should now look like:

<wavelet-estimation-interval>
   <top-surface>
       <time-file>  surface.txt </time-file>
  </top-surface>

<wavelet-estimation-interval>
 <top-surface>
       <time-value>  1500 </time-value>
 </top-surface>

The gui needs to be updated accordingly.

Inputting "Correlation direction" in the Horizons tab: The "Files of type" in the file browser is set to "Correlation file (_storm)" by default, should be the "Surface file (_storm, *irap, *Sgri)".

This should also be fixed for surfaces under Multizone background model, these are said to be "Seismic file" but should be "Surface file"

When reading in a model file using File -> Open, tags <time-value> under <interval-two-surfaces> are not read.

Seems to be read correctly from 'Open previous project'.

In wells tab, when "Use separate names for logs in this well" is unticked, have coordinate settings visible and allow setting tags common for all wells. Tags will have to be added accordingly under log-names.

Input for "Angular correlation" under "Survey information" should be a 1D variogram, but the input allows for 2D properties. The options "Subrange" and "Angle" should be removed.

Also, "Power" is not an allowed parameter for a spherical variogram.

However, before this can be implemented, it needs to be agreed exactly how the gui should implement this functionality.

The "Apply to all stacks" button should only apply to the "User defined" "Header format information (in the "Survey information" tab).

I suggest moving the button underneath "Ignore coordinate scaling" and it should only be visible when "User defined" is chosen.

The button should be renamed "Apply format to all stacks" and only change "Inline", "Crossline", "x-coordinate", "y-coordinate" and "Ignore coordinate scaling" for all stacks.

Same folder used as working directory and input directory are equal, then saving the xml-file will append the name of the input folder and save in the folder above the input folder.

In advanced-settings: Tag is spelled energy-treshold, should be energy-threshold

set to shperical. Should be spherical.

In the "Output" tab the description "Input xml-filename" should be changed to "Project name" as this is a more intuitive description.

The tags <high-cut-background-modelling> and <lateral-correlation> should be available for the Multizone bakground model the same way that they are for the original background model ("Configure estimated background"). "Vp trend from file" should NOT be available for the Multizone background model.

Two new tags implemented. It is location-start-time under segy-format, both under seismic-data and grid-output. It is used for manually setting the location if it differ from the standard format, similar to the other location-xx tags.

These are not exposed in the gui, but they do not break either, so the gui should produce runnable xml-files.

This is reported in CRAVA/crava#220

The surface uncertainty of the base surface of the lowest zone need to be zero, and the GUI is coded such that you cannot change the surface uncertainty of the lowest zone. The problem is that every time you add a new zone you may want to finish this zone before creating a new one, but you cannot change the surface uncertainty before you add a new zone.

In the Multizone background model each surface needs to be given a unique erosion priority. At the moment all surfaces are given erosion priority 1 and it is not intuitive for the user that he needs to change these and give them a unique value.

It should be possible to open a previous run simply by doing:
$ cravagui myfile.xml

The GUI often crashes with Segmentation fault when clicking "Add Optimization" under "Optimize position for this well" several times. No specific pattern/trigger is found.

In the "Prior Model" tab there should be a button for "Use absolute elastic parameters" (together with "Use Vs for facies probability" and "Use sampled inversion logs instead of filtered well logs for facies probability"). The tag is available in the xml-tree, but there is no button for it in the GUI.

The GUI does not read the correlation direction in an xml-file properly. When opening a previous project (xml-file), the tag <correlation-direction> under <lateral correlation> will not be read and is left empty in the GUI.

There are two settings for wavelets, format and which wavelets to output. If a format is specified without requesting a type of wavelet, CRAVA will not run. The default is to request a wavelet format, but no output wavelet, which fails.

If a wavelet format, e.g. JASON, is unchecked, the GUI will create a model file with "no" for the tag <jason>. If no is chosen for all formats, no wavelet will be written to file even if they are requested under output.

CRAVA has sensible default values if there is no information about the formats, so the default should be not to request a format and that this leads to no <format> tag in the model file.

To be more specific, this is the default in the GUI:

<wavelet-output>
<format>
<jason>yes</jason>
<norsar>no</norsar>
</format>
</wavelet-output>

which crashes since we ask for a format without specifying an output.

This is what it looks like if we uncheck both the format boxes and ask for output of well wavelets:

<wavelet-output>
<format>
<jason>no</jason>
<norsar>no</norsar>
</format>
<well-wavelets>yes</well-wavelets>
</wavelet-output>

which will run, but won't output a wavelet since we say no to both formats.

This is how I want it to look if both format boxes are unchecked:

<wavelet-output>
<well-wavelets>yes</well-wavelets>
</wavelet-output>

The default in the GUI should also be to have both boxes unchecked.

Power should not be an allowed parameter for spherical variograms, only for General exponential.

At the moment, there is no good link between a parameter file and the inversion results. How about using the project name from the GUI (which is also the file name of the xml file) as part of the CRAVA output?
If, for example, the project name is "MyProject", then all output should also contain the "MyProject"

• the log file could be MyProject_log.txt
• wavelets could be MyProject_wavelat_stackXYZ.wlt
• inversion results could be MyProject_predicted_VP.sgy
• ...
  That way, you would also avoid the danger of accidently overwriting previous files ...

If you save before clicking the 'Run'-button, e.g., by Ctrl+S, no terminal window will open and crava will not run. This might happen because the 'Run'-button prompts you to save the document and this fails if the model file has already been saved.

Horizon-tab:

• If "Number of Layers" are not set in first run (run 1), Crava makes its own number (302), dependent of the Correlation direction ==> OK! BUT: When rerunning the Crava (run 2) with the same "number of layers" (302) as Crava gave in the first run (run 1), the "number of layers" are being resampled ( to 318) due to correlation direction....but the surface direction has not been changed in run 2 compared to run 1. Shouldn't the "number of layers" then be kept the same in run 2 as it was "defaulted by Crava" in run 1? Ex:

***** Setting up multiple interval grid ***** (taken from logfile)

RUN 1: Creating extended simbox with one correlation surface for interval 'zone 1'.
Z padding sizes estimated from an assumed wavelet length for interval 'zone 1':
zPad, zPadFac, nz, nzPad : 200ms, 0.192, 302, 360

Run 2:Creating extended simbox with one correlation surface for interval 'zone 1'.
Number of layers in interval zone 1 increased from 302 to 318 because of the correlation direction.
Z padding sizes estimated from an assumed wavelet length for interval 'zone 1':
zPad, zPadFac, nz, nzPad : 200ms, 0.179, 318, 375

<background-trend-1d> is no longer an option, should be removed from tree and from the Output pane ("Background trend as 1D curve").