crash of conventional 3C FK in 3.3.3

This forum is dedicated to discuss all problems and suggestions related to the use of geopsy database and its plugins (array processing, H/V,...).
Post Reply
marzeck
Posts: 4
Joined: Wed Jul 08, 2020 3:26 pm

crash of conventional 3C FK in 3.3.3

Post by marzeck »

Hi,

As I cannot send a crash report from Geopsy itself still, here is the crash report. When using the 3C version of FK in 3.3.3 the "passive RTBF" and "passive RTBF radial" work fine. But when I try to run the "passive conventional" the whole program chrashes.

Interestingly when just using the vertical data of the same data-set, the Geopsy FK GUI doesn't allow me to choose "passive conventional", only "passive HR". If I want to choose it, the drop-down will take "active HR".

<CrashReport>
<Error>
<severity>--FATAL ERROR- </severity>
<message>Abort Signal</message>
<time>2020-10-29 12:09:23.767</time>
<threads>main,layerPainter1,layerPainter2,layerPainter3,layerPainter4,layerPainter5,layerPainter6,layerPainter7,layerPainter8,LoopWorker_0,LoopWorker_1,LoopWorker_2,LoopWorker_3,LoopWorker_4,LoopWorker_5,LoopWorker_6,LoopWorker_7</threads>
<currentThread>LoopWorker_1</currentThread>
<stack>QGpCoreTools::CoreApplicationPrivate::backTrace()
QGpCoreTools::CoreApplicationPrivate::bugInfo(QGpCoreTools::Message::Severity, QString const&amp;)
QGpCoreTools::CoreApplicationPrivate::reportBugNow(QGpCoreTools::Message::Severity, QString const&amp;)
QGpCoreTools::CoreApplicationPrivate::osSignal(int)




qt_assert_x(char const*, char const*, char const*, int)

ArrayCore::ConvFKRayleigh::value(QGpCoreMath::Point const&amp;) const
QGpCoreMath::GridSearch::refineMax(QGpCoreMath::Point const&amp;, QGpCoreMath::Point const&amp;, double)
QGpCoreMath::GridSearch::globalMax(double)
ArrayCore::FKWorker::process(QVector&lt;int&gt; const&amp;)
ArrayCore::ArrayWorker::process(QGpCoreTools::AbstractTask*)
QGpCoreTools::TaskWorker::run(int)
QGpCoreTools::LoopWorker::run()



</stack>
<bugStack>---- thread main
---- thread layerPainter1
---- thread layerPainter2
---- thread layerPainter3
---- thread layerPainter4
---- thread layerPainter5
---- thread layerPainter6
---- thread layerPainter7
---- thread layerPainter8
---- thread LoopWorker_0
---- thread LoopWorker_1
---- thread LoopWorker_2
---- thread LoopWorker_3
---- thread LoopWorker_4
---- thread LoopWorker_5
---- thread LoopWorker_6
---- thread LoopWorker_7
---- thread main
---- thread layerPainter1
---- thread layerPainter2
---- thread layerPainter3
---- thread layerPainter4
---- thread layerPainter5
---- thread layerPainter6
---- thread layerPainter7
---- thread layerPainter8
---- thread LoopWorker_0
---- thread LoopWorker_1
---- thread LoopWorker_2
---- thread LoopWorker_3
---- thread LoopWorker_4
---- thread LoopWorker_5
---- thread LoopWorker_6
---- thread LoopWorker_7
</bugStack>
</Error>
<application>geopsy</application>
<version> Qt 5.12.8
QGpCoreTools 2.3.2 from 3.3.3
(commit 1001aa3e175620e74285f193b2f52e1713bd2263)
QGpCoreMath 1.3.1 from 3.3.3
(commit 690aa9eb4c99f411b15e6b8abfcc1d009de99d5d)
GeopsyCore 4.3.2 from 3.3.3
(commit d412b917efb581b6181b848aa632573e4fda7a75)
GeopsySLink 2.0.2 from 3.3.3
(commit b79d3ec8da109800bb3514cd03a41e68a988ae4f)
QGpGuiTools 2.3.1 from 3.3.3
(commit c43f97d3fca6838dea01637fe348ed27b2ac5cb0)
SciFigs 3.2.1 from 3.3.3
(commit f6ace81574ecad281d9d90b35fa6c953672d3dba)
GeopsySLinkGui 2.0.2 from 3.3.3
(commit c992b6abeb468bb7ffb8f2c5cf70f70e5f5dce91)
QGpGuiMath 1.2.0 from 3.3.3
(commit fcb2db028ddd8468aac76215daa15e0f3913a00a)
GeopsyGui 3.3.2 from 3.3.3
(commit cdaf398a150ded796b93a7558003193eb8be87d9)
geopsy 3.3.2 from 3.3.3
(commit f249f2e8d85275ff2694f5c949ae38339afc3974)
geopsyfigs 1.0.1 from 3.3.3
(commit 4631838734ff4e18a5da918c75b687f81c8b8c69)
campbelltob3 1.0.1 from 3.3.3
(commit f2f3682c002a3b8e2252f00834d11219dad6a65a)
DinverCore 1.2.2 from 3.3.3
(commit 1a012724174bfb13ffc14ce6430120c5f98727e6)
QGpCoreStat 1.1.0 from 3.3.3
(commit eebf08c0598221888104b876dac8a61b30d60441)
QGpCoreWave 2.1.2 from 3.3.3
(commit c2d48fd8c403275191cb4a4ca6b14bf24033bc04)
QGpCompatibility 1.1.0 from 3.3.3
(commit ecc6d91e29d4105b0e82e12ed24acff6c48d2ed8)
DinverDCCore 2.1.1 from 3.3.3
(commit 9199c63c7b8adcf8277cb65a5d65edb877be26aa)
QGpGuiWave 1.1.0 from 3.3.3
(commit 60dd9eab4bc6d348fab34a7b874ac704979495a8)
ArrayCore 4.0.3 from 3.3.3
(commit 35bfc8829edd50529daf0bf212a1b6aefa2a3b2b)
ArrayGui 1.2.1 from 3.3.3
(commit b843aa9d9163c8173994f562e819daf5701fbe5b)
geopsyarray 3.2.1 from 3.3.3
(commit ad36c6e4443e7e5c88542574509ba201a86032ac)
geopsydamping 2.1.1 from 3.3.3
(commit 9ccebd2898be21ee56f866774fdc23a1a211bdff)
HVCore 1.0.2 from 3.3.3
(commit 70f210ee7d70edd020e6adbeff4e5240cdd829e6)
HVGui 1.0.0 from 3.3.3
(commit 3a8d1846879a68ba28e4fd5a2e1a46d16ec04f87)
geopsyhv 4.0.0 from 3.3.3
(commit 4ccb5a1ce6ab88f1f6fffc574e70e3485909a970)
geopsynr 1.1.0 from 3.3.3
(commit d5ed961018c8927c6fd19a6f2978d304b26e0642)
geopsyptmotion 2.0.2 from 3.3.3
(commit e04d740f09629e1b0b7eb965f6de40bc322c689f)
geopsyrefra 2.0.1 from 3.3.3
(commit 47286bdb8d13cfc21a89a20d313d3308452f1770)
geopsytfa 2.1.0 from 3.3.3
(commit 350fe3d0f8b017f193b7985b8a0b8cf39fa562e1)
hvtfa 2.1.1 from 3.3.3
(commit 0c814bb9ab0b56b4366c25e27936ff2d040e873d)
matfiles 1.0.2 from 3.3.3
(commit 6fe821ab81d07b4a6bf1d056e53cd54055e53293)
</version>
<system>linuxmint 20</system>
</CrashReport>



Cheers,
marzeck

admin
Site Admin
Posts: 524
Joined: Mon Aug 13, 2007 11:48 am
Location: ISTerre
Contact:

Re: crash of conventional 3C FK in 3.3.3

Post by admin »

Thanks for your report.
I could reproduce all the mentioned errors. They will be fixed for the next release.
If you are compiling from sources (Linux and Mac OS), you can switch to git repository (see download page) to get the most up-to-date release under preparation (3.3.4-preview). These fixes will be available in a few hours.

Best regards,

Marc

marzeck
Posts: 4
Joined: Wed Jul 08, 2020 3:26 pm

Re: crash of conventional 3C FK in 3.3.3

Post by marzeck »

Hi,

I've switched and compiled from the repository, but as I was not able to checkout the 3.3.4-preview I directly tested with the 3.4 version. I've added the crash report, as in that version the conventional FK for 3 components still fails.

Hope that helps.
Attachments
crash-report-3.4-pre.txt
(7.17 KiB) Downloaded 20 times

admin
Site Admin
Posts: 524
Joined: Mon Aug 13, 2007 11:48 am
Location: ISTerre
Contact:

Re: crash of conventional 3C FK in 3.3.3

Post by admin »

Hi,

I wrote that it will be fixed soon but I had to switch to something else and I left it unfixed.
Now things are fine. It is available on branch 3.3 on the git repository. It is not yet merged into branch 3.4. Hence 3.3.4-preview only.

Note that conventional FK for 3C can retrieve only the sign of the ellipticiy and not the value. High resolution RTBF provide both.

Regards,

Marc

Post Reply