geopsy.org

Hi,
I have verified that with version 3.3.1. of Geopsy it is not possible to use the Spac2disp tool because the program crashes. The bug report is not transmissible because a message appears saying that I am not using the last version of the program. This is not true because 3.3.1. is the latest release currently available. So I can only see the autocorrelation ratio graphs with Dinver for the different radii, but I can't to save the final autocorrelation ratio curve as shown in technical documentation.
Is it possible to verify the nature of the bug? I attach an image and the report.
Thank you
Luigi
I tried to send the bug report from the Bug section but I had the same answer (upgrade to the last relaese). Why that happens?
So I send you in this fashion the crash report and I hope a developper can see it and solve.
<CrashReport>
<Error>
<severity>--FATAL ERROR- </severity>
<message>ASSERT: &quot;_sorted&quot; in file c:/Geopsy/distribs/src/testing/geopsypack/QGpCoreMath/src/Curve.h, line 371</message>
<time>2020-07-25 10:15:50.192</time>
<threads>main,layerPainter1,layerPainter2,layerPainter3,layerPainter4,layerPainter5,layerPainter6,layerPainter7,layerPainter8</threads>
<currentThread></currentThread>
<stack>---- thread main
void SpacSelector::inverse():279
bool SpacSelector::createObjects(QGpCoreWave::AutocorrCurves*):113
---- thread layerPainter1
virtual void SciFigs::LayerPainterThread::run():59
---- thread layerPainter2
virtual void SciFigs::LayerPainterThread::run():59
---- thread layerPainter3
virtual void SciFigs::LayerPainterThread::run():59
---- thread layerPainter4
virtual void SciFigs::LayerPainterThread::run():59
---- thread layerPainter5
virtual void SciFigs::LayerPainterThread::run():59
---- thread layerPainter6
virtual void SciFigs::LayerPainterThread::run():59
---- thread layerPainter7
virtual void SciFigs::LayerPainterThread::run():59
---- thread layerPainter8
virtual void SciFigs::LayerPainterThread::run():59
</stack>
<bugStack>---- thread main
---- thread layerPainter1
---- thread layerPainter2
---- thread layerPainter3
---- thread layerPainter4
---- thread layerPainter5
---- thread layerPainter6
---- thread layerPainter7
---- thread layerPainter8
---- thread main
---- thread layerPainter1
---- thread layerPainter2
---- thread layerPainter3
---- thread layerPainter4
---- thread layerPainter5
---- thread layerPainter6
---- thread layerPainter7
---- thread layerPainter8
</bugStack>
</Error>
<application>spac2disp</application>
<version> Qt 5.12.3
QGpCoreTools 2.3.0 from 3.3.1
(commit 2fd9273a64b340d3fcdd50e415102912c4669cab)
QGpCoreMath 1.3.0 from 3.3.1
(commit e1c2a7248a8017a7d5c2fdf1f5513fd8a7568641)
DinverCore 1.2.1 from 3.3.1
(commit 86417be737e760f8c273b747469fe48008ac0b1f)
QGpCoreWave 2.1.0 from 3.3.1
(commit 48b3a8c35c9cd399dd1825070984cb0ca0584fc9)
QGpCompatibility 1.1.0 from 3.3.1
(commit 640d291239131690dac044516ee64ce5f134ffb3)
DinverDCCore 2.1.0 from 3.3.1
(commit 178068944cd0c32c8ccc6199fd1a2dcb85718206)
QGpGuiTools 2.3.0 from 3.3.1
(commit 9c611db00b72a88ec0f5d5793b2437494f723235)
SciFigs 3.2.0 from 3.3.1
(commit f75cfa2444beb3c54b08b3bf153ee5c4d212a1bb)
QGpGuiMath 1.2.0 from 3.3.1
(commit 24ee3579f5ff531652dc0f851fa1659b931020ec)
QGpGuiWave 1.1.0 from 3.3.1
(commit a407664ae22435e4e96e2511d6d8cad22824cf05)
spac2disp 1.0.1 from 3.3.1
(commit a8675767177121cc114991ddd49dd140a6d92c5a)
</version>
<system>windows 10</system>
</CrashReport>

Hi Luigi,

The bug report facility has to be checked. I know it is not working properly.
For spac2disp, I was not aware of the problem. Thanks for your report. It is a question of days before I release 3.3.2 because MASW active FK has also some blocking issues. spac2disp will be fixed.

Marc

Thanks for answer.

I have tried these days with previous versions of Geopsy and also 3.3.0. and snapshot-20161121 don't open the spac2disp tool. I only did it with 2.9.0. which apparently works correctly, but does not have the autopick utility. Furthermore, when I activate the "select" option, a warning message appears: "Less than 2 curves are visible, cannot define the slowness range. Pick at least two curves to define the minimum and maximum range for dispersion curves". And this message also appears in the snapshot version which, however, saves the file without frequencies and is therefore unreadable by dinver. In any case I managed to conclude the inversion of the auto-correlation curves of the Lep_ring01 database and I would like to see, since there is no documentation, the correspondence, or not, with your final result. However, I noticed that the dispersion curve obtained with RTBF seems to me to be more complete and better defined than the SPAC one. It's correct?
Thanks for your patience and courtesy.
Luigi

Hi Marc,

I can reproduce the crash problem of spac2disp for linux. Independent from wether it is called through the commandline with the target file directly or after selecting the target file through the GUI.

Cheers,
Martin

Hi Martin,

Did you try with 3.3.2? I think that most of the issues have been solved with this version.

Hi Marc,

Sorry for the late response. After updating to the newest version 3.3.3 this issue still remains the same. I just installed it three days ago and cannot send a crash report still.

marzeck

Hi,

The facility for collecting crash reports has not worked for a long time. Still need to repair it but time goes fast. I checked with 3.3.4-preview with no problem. When does it happen? Right on start-up? Can you send me your .taget file?

Best regards,

Marc