SeisTrcWriter dump

[Fernando Bordignon]

Hello everyone, how are you doing?

Recently a potential client contacted us needing to run seismic inversion on a 25GiB angle stack dataset (3x25GiB seismic + 3x25GiB elastic property trends).

The problem is that our plugin was storing the inverted traces on a few SeisTrcBuf objects. I've managed to implement a pooling mechanism to consume the buffer and delete the traces as I sent them to SeisTrcWriter objects. However, SeisTrcWriter is keeping a copy of the traces inside it (trcblock_) and still taking up a lot of memory. How can I dump the written traces from SeisTrcWriter? Is there another way to write humongous cubes using less memory as the data become available to write? I need to write it without caching the whole cube in memory, since the inversion is producing 150GiB of data.

Thanks!

[Raman Singh]

Hi Fernando,

I guess you are talking about SeisTrcTranslator::trcblock_. This buffer is deleted in both SeisTrcTranslator::writeBlock() and SeisTrcTranslator::dumpBlock() functions:

trcblock_.deepErase();

I suspect something else is going wrong here. If you privately share your code snippet (the part where you use the SeisTrcWriter, I can take a closer look.

Best regards,

Raman

--
You received this message because you are subscribed to the Google Groups "OpendTect Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to developers+...@opendtect.org.
To view this discussion on the web visit https://groups.google.com/a/opendtect.org/d/msgid/developers/147eb766-de38-4285-bba9-07a303946871n%40opendtect.org.

--

 Raman K Singh

VP Software Development

-----------------------------------------------------------------------------------------------------------------------   dGB Earth Sciences
Phone: +1 281 240 3939 E-mail: raman...@dgbes.com Internet: dgbes.com

-----------------------------------------------------------------------------------------------------------------------  

[Fernando Bordignon]

Hi Raman, you are totally right. Thanks for helping me out. Turns out it was a bug in my code. I just needed to vent a little bit 😂

Since we are in the subject, can we do a seismic write function that takes ownership of the trace, write it and delete it? It would avoid many unnecessary copies in my case.

Regards, Fernando.

You received this message because you are subscribed to a topic in the Google Groups "OpendTect Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/a/opendtect.org/d/topic/developers/uE0CnbRLwwQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to developers+...@opendtect.org.
To view this discussion on the web visit https://groups.google.com/a/opendtect.org/d/msgid/developers/CAJAPLGEEQ3fYM6FBTq-6sOjksRaO5CfVDP6QMj%2BLzwbuxcJN2A%40mail.gmail.com.