Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. POProhibited from accessing other seismic data in attribute generator (2011)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USEvgeny
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks, Evgeny. Trace or brick based doesn't matter. I used CanGenerateAsync in Petrel 2010 in order to be able to access domain objects (arbitrary volumes) other than the input ISubCubes, as the generator was then running in the UI thread. I simply use SeismicCube to access ISubCubes matching the ISubCube of the output volume. This is all a workaround in order to be able to generate an attribute from an *arbitrary* number of inputs, since the amount of volumes provided by the user is unknown at build time. Thus, I can't use InputCount, as the amount is neither known or constant.
      singulars
      1. PO
      1. USRobert Schmidt
    2. COSorry, I meant CanGenerateAsync==false above. My issue highlights a weakness in the attributes API - it now appears that our only option (in Petrel 2011) for deriving a volume from a *dynamic* number of inputs, is to perform the entire calculation up front. I can find no way to perform the calculation on demand. This places a potentially huge investment of time (and disk space) on the user before (s)he can even assess the correctness of the calculation parameters.
      singulars
      1. PO
      1. USRobert Schmidt
    3. COI thought I'd elaborate on a use case: seismic stochastic inversion produces a user-configurable number of impedance realizations, typically also in pairs (IP/IS or AI/GI). Typical post processing of these realizations include calculating statistics across all or some of them. If seismic attributes supported a dynamic InputCount, they'd be the perfect vehicle for such post processing.
      singulars
      1. PO
      1. USRobert Schmidt
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload