Dear FSL experts,
I have been running group melodic on our university's high performance computer and have been running into some issues when I run d - 50 or above. I have tried lower d values (25 and 30) and these run fine. For d - 50 and above Melodic aborts on these high d runs about an hour into the job because it cant allocate enough memory at some stage. However I am requesting over 1TB of memory in my pbs script. Below is the traceback from the report file that melodic produces
#4 0x00002b51bc017141 in std::terminate() ()
at ../../.././libstdc++-v3/libsupc++/eh_terminate.cc:57
#5 0x00002b51bc0173a6 in __cxa_rethrow ()
at ../../.././libstdc++-v3/libsupc++/eh_throw.cc:125
#6 0x00000000005e154b in NEWMAT::StackedMatrix::Evaluate(NEWMAT::MatrixType)
() at newmat7.cxx:857
#7 0x00000000005d8e25 in NEWMAT::GeneralMatrix::Eq2(NEWMAT::BaseMatrix const&, NEWMAT::MatrixType) () at newmat4.cxx:660
#8 0x00000000005def40 in NEWMAT::GeneralMatrix::operator&=(NEWMAT::BaseMatrix const&) () at newmat6.cxx:705
#9 0x0000000000434b85 in Melodic::MelodicData::setup_classic() ()
at meldata.cc:548
#10 0x0000000000439705 in Melodic::MelodicData::setup() () at meldata.cc:644
#11 0x0000000000467c45 in main () at melodic.cc:144
I would really appreciate any suggestions to sort this problem out.
kind regards
Kathryn
|