Matlab Compatability

67 views
Skip to first unread message

tanvi.j...@gmail.com

unread,
Oct 27, 2019, 12:37:47 PM10/27/19
to ecg-kit users
Hello,

I am using Matlab version 2019B to run the ECG kit and am running into some problems while trying to run the examples. What is the best version to run this kit on?

Mariano Llamedo Soria

unread,
Oct 27, 2019, 12:43:51 PM10/27/19
to tanvi.j...@gmail.com, ecg-kit users
Hi tanvi, thanks flor trying the kit. The last MATLAB i used was 2018. This is compatible for sure, i am not aware of recent updates since we are updating the kit for python.

Best
M

El dom., 27 de oct. de 2019 13:37, <tanvi.j...@gmail.com> escribió:
Hello,

I am using Matlab version 2019B to run the ECG kit and am running into some problems while trying to run the examples. What is the best version to run this kit on?

--
You received this message because you are subscribed to the Google Groups "ecg-kit users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ecg-kit-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ecg-kit-users/ded27206-281e-4490-a94f-0c335fc27e08%40googlegroups.com.

tanvi.j...@gmail.com

unread,
Oct 27, 2019, 12:45:33 PM10/27/19
to ecg-kit users
Thank you for your response! Which version of 2018 would you recommend, A or B?

Mariano Llamedo Soria

unread,
Oct 27, 2019, 12:56:32 PM10/27/19
to tanvi.j...@gmail.com, ecg-kit users
Try A, ir You have further issues, feel free yo ask.

Good luck
M

--
You received this message because you are subscribed to the Google Groups "ecg-kit users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ecg-kit-user...@googlegroups.com.

tanvi.j...@gmail.com

unread,
Oct 27, 2019, 2:56:56 PM10/27/19
to ecg-kit users
I will try 2018A. Which additional toolboxes and compilers are needed, if any?


On Sunday, October 27, 2019 at 12:37:47 PM UTC-4, tanvi....@gmail.com wrote:

jta...@umich.edu

unread,
Oct 27, 2019, 5:38:39 PM10/27/19
to ecg-kit users
Hello,

I tried 2018A on Windows 10 and installed the MEX compiler but it crashes when I run the ECGw.Run command. Do you know what could be causing this? I have pasted the output below:


ECGw.Run

Description of the process:
 + Recording: recordings\example_recording.mat
 + Task name: QRS_detection                    

Processing QRS detector aristotle

###############################################
# Could not execute "aristotle" QRS detector. #
###############################################

Processing QRS detector ecgpuwave

--------------------------------------------------------------------------------
          Access violation detected at Sun Oct 27 05:30:29 2019 -0400
--------------------------------------------------------------------------------

Configuration:
  Crash Decoding           : Disabled - No sandbox or build area path
  Crash Mode               : continue (default)
  Default Encoding         : windows-1252
  Deployed                 : false
  Graphics Driver          : Intel Intel(R) HD Graphics 5500 Version 4.4.0 - Build 20.19.15.4642
  Graphics card 1          : Intel Corporation ( 0x8086 ) Intel(R) HD Graphics 5500 Version 20.19.15.4642 (2017-3-28)
  Java Version             : Java 1.8.0_144-b01 with Oracle Corporation Java HotSpot(TM) 64-Bit Server VM mixed mode
  MATLAB Architecture      : win64
  MATLAB Entitlement ID    : 3630646
  MATLAB Root              : C:\MATLAB\R2018a
  MATLAB Version           : 9.4.0.813654 (R2018a)
  OpenGL                   : hardware
  Operating System         : Microsoft Windows 10 Home
  Process ID               : 532
  Processor ID             : x86 Family 6 Model 61 Stepping 4, GenuineIntel
  Session Key              : cb05f08c-ba0d-4902-baf7-ad8c761a67e2
  Window System            : Version 10.0 (Build 17134)

Fault Count: 1


Abnormal termination

Register State (from fault):
  RAX = 0000000000000000  RBX = 00007fffc03cfa90
  RCX = 00000000ffffffff  RDX = 0000000000000003
  RSP = 00000000043fafe0  RBP = 00000000043fb060
  RSI = 0000000000000000  RDI = 0000000000000000
 
   R8 = 00007fffc03d5920   R9 = 00000000043fb060
  R10 = 0000000000000000  R11 = 0000000000000246
  R12 = 000000000ea9bc20  R13 = 000000000e737d00
  R14 = 0000000000000001  R15 = 0000000000000000
 
  RIP = 0000000010371ac4  EFL = 00010257
 
   CS = 0033   FS = 0053   GS = 002b

Stack Trace (from fault):
[  0] 0x0000000010371ac4 C:\TanviProject\ecg-kit-0.1.6\common\readannot.mexw64+00006852 mexFunction+00001556
[  1] 0x00000000fc626594                               bin\win64\libmex.dll+00288148 MexRetrieveVersion+00002916
[  2] 0x00000000fc62678c                               bin\win64\libmex.dll+00288652 MexRetrieveVersion+00003420
[  3] 0x00000000fc6268de                               bin\win64\libmex.dll+00288990 MexRetrieveVersion+00003758
[  4] 0x00000000fc612ec3                               bin\win64\libmex.dll+00208579 mexUnlock_800+00024147
[  5] 0x00000000165ec51a                     bin\win64\pgo\m_dispatcher.dll+00050458 Mfh_file::dispatch_fh_impl+00001114
[  6] 0x00000000165ec0b2                     bin\win64\pgo\m_dispatcher.dll+00049330 Mfh_file::dispatch_fh+00000062
[  7] 0x00000000165e4674                     bin\win64\pgo\m_dispatcher.dll+00018036 Mfunction_handle::dispatch+00000420
[  8] 0x00000000174c0189                            bin\win64\pgo\m_lxe.dll+00393609
[  9] 0x000000001754a808                            bin\win64\pgo\m_lxe.dll+00960520 mwboost::serialization::singleton<mwboost::archive::detail::pointer_iserializer<mwboost::archive::binaryTerm_iarchive,ir::IrTree> >::get_instance+00121832
[ 10] 0x000000001754b403                            bin\win64\pgo\m_lxe.dll+00963587 mwboost::serialization::singleton<mwboost::archive::detail::pointer_iserializer<mwboost::archive::binaryTerm_iarchive,ir::IrTree> >::get_instance+00124899
[ 11] 0x000000001754c836                            bin\win64\pgo\m_lxe.dll+00968758 mwboost::serialization::singleton<mwboost::archive::detail::pointer_iserializer<mwboost::archive::binaryTerm_iarchive,ir::IrTree> >::get_instance+00130070
[ 12] 0x000000001754d3f0                            bin\win64\pgo\m_lxe.dll+00971760 mwboost::serialization::singleton<mwboost::archive::detail::pointer_iserializer<mwboost::archive::binaryTerm_iarchive,ir::IrTree> >::get_instance+00133072
[ 13] 0x000000001754c97f                            bin\win64\pgo\m_lxe.dll+00969087 mwboost::serialization::singleton<mwboost::archive::detail::pointer_iserializer<mwboost::archive::binaryTerm_iarchive,ir::IrTree> >::get_instance+00130399
[ 14] 0x000000001754ca7e                            bin\win64\pgo\m_lxe.dll+00969342 mwboost::serialization::singleton<mwboost::archive::detail::pointer_iserializer<mwboost::archive::binaryTerm_iarchive,ir::IrTree> >::get_instance+00130654
[ 15] 0x00000000174ce8a5                            bin\win64\pgo\m_lxe.dll+00452773
[ 16] 0x00000000174cb335                            bin\win64\pgo\m_lxe.dll+00439093
[ 17] 0x00000000174ca82e                            bin\win64\pgo\m_lxe.dll+00436270
[ 18] 0x00000000174d1b9a                            bin\win64\pgo\m_lxe.dll+00465818
[ 19] 0x00000000174d133d                            bin\win64\pgo\m_lxe.dll+00463677
[ 20] 0x00000000174d144e                            bin\win64\pgo\m_lxe.dll+00463950
[ 21] 0x0000000017671d9c                            bin\win64\pgo\m_lxe.dll+02170268 mwboost::serialization::singleton<mwboost::archive::detail::pointer_oserializer<mwboost::archive::binary_oarchive,MathWorks::lxe::PreLineExecutionEvent> >::get_instance+00475644
[ 22] 0x0000000017671d4a                            bin\win64\pgo\m_lxe.dll+02170186 mwboost::serialization::singleton<mwboost::archive::detail::pointer_oserializer<mwboost::archive::binary_oarchive,MathWorks::lxe::PreLineExecutionEvent> >::get_instance+00475562
[ 23] 0x00000000174a051d                            bin\win64\pgo\m_lxe.dll+00263453
[ 24] 0x00000000167f8acf                    bin\win64\pgo\m_interpreter.dll+00297679 inEvalCmdWithLocalReturn+00000063
[ 25] 0x00000000fb60bedb                          bin\win64\libmwbridge.dll+00114395 mnParser+00001595
[ 26] 0x0000000016436564                                  bin\win64\mcr.dll+00222564 mcr::runtime::setInterpreterThreadSingletonToCurrent+00091332
[ 27] 0x00000000164397ae                                  bin\win64\mcr.dll+00235438 mcr::runtime::setInterpreterThreadSingletonToCurrent+00104206
[ 28] 0x0000000016456c8a                                  bin\win64\mcr.dll+00355466 mcrRegisterExternalFunction+00007930
[ 29] 0x00000000164589bc                                  bin\win64\mcr.dll+00362940 mcrRegisterExternalFunction+00015404
[ 30] 0x0000000016455bff                                  bin\win64\mcr.dll+00351231 mcrRegisterExternalFunction+00003695
[ 31] 0x0000000016456c46                                  bin\win64\mcr.dll+00355398 mcrRegisterExternalFunction+00007862
[ 32] 0x0000000016455ce3                                  bin\win64\mcr.dll+00351459 mcrRegisterExternalFunction+00003923
[ 33] 0x0000000016458ff6                                  bin\win64\mcr.dll+00364534 mcrRegisterExternalFunction+00016998
[ 34] 0x00000000fd014f67                                  bin\win64\iqm.dll+00544615 iqm::IqmPlugin<cmddistributor::PackagedTaskIIP>::getIIP+00016215
[ 35] 0x00000000fd01567f                                  bin\win64\iqm.dll+00546431 iqm::PackagedTaskPlugin::execute+00000911
[ 36] 0x00000000fd014fed                                  bin\win64\iqm.dll+00544749 iqm::IqmPlugin<cmddistributor::PackagedTaskIIP>::getIIP+00016349
[ 37] 0x00000000fd0154c3                                  bin\win64\iqm.dll+00545987 iqm::PackagedTaskPlugin::execute+00000467
[ 38] 0x00000000fcfed9ea                                  bin\win64\iqm.dll+00383466 iqm::Iqm::setupIqmFcnPtrs+00071994
[ 39] 0x00000000fcfed84c                                  bin\win64\iqm.dll+00383052 iqm::Iqm::setupIqmFcnPtrs+00071580
[ 40] 0x00000000fcfce722                                  bin\win64\iqm.dll+00255778 iqm::Iqm::deliver+00003730
[ 41] 0x00000000fcfcf749                                  bin\win64\iqm.dll+00259913 iqm::Iqm::deliver+00007865
[ 42] 0x00000001001aa211                        bin\win64\libmwservices.dll+01810961 services::system_events::PpeDispatchHook::dispatchOne+00030865
[ 43] 0x00000001001b7ff3                        bin\win64\libmwservices.dll+01867763 sysq::addProcessPendingEventsUnitTestHook+00004659
[ 44] 0x00000001001b81e0                        bin\win64\libmwservices.dll+01868256 sysq::addProcessPendingEventsUnitTestHook+00005152
[ 45] 0x00000001001b9576                        bin\win64\libmwservices.dll+01873270 sysq::getCondition+00003446
[ 46] 0x00000001001bb0e6                        bin\win64\libmwservices.dll+01880294 svWS_ProcessPendingEvents+00000230
[ 47] 0x0000000016440737                                  bin\win64\mcr.dll+00263991 mcr::runtime::setInterpreterThreadSingletonToCurrent+00132759
[ 48] 0x0000000016442360                                  bin\win64\mcr.dll+00271200 mcr::runtime::setInterpreterThreadSingletonToCurrent+00139968
[ 49] 0x000000001641e9b7                                  bin\win64\mcr.dll+00125367 mcr_process_events+00001959
[ 50] 0x00000000162efef5                             bin\win64\MVMLocal.dll+00327413 mvm_server::inproc::LocalFactory::terminate+00139589
[ 51] 0x00000000fa9605b9                                  bin\win64\mvm.dll+01246649 mvm::detail::initLocalMvmHack+00000793
[ 52] 0x00000000fa960dcb                                  bin\win64\mvm.dll+01248715 mvm::detail::SessionImpl::privateSession+00000555
[ 53] 0x00000000fa960ff1                                  bin\win64\mvm.dll+01249265 mvm::detail::SessionImpl::privateSession+00001105
[ 54] 0x000000014000780d                               bin\win64\MATLAB.exe+00030733
[ 55] 0x000000014000862f                               bin\win64\MATLAB.exe+00034351
[ 56] 0x00007fffbfe14034                   C:\WINDOWS\System32\KERNEL32.DLL+00081972 BaseThreadInitThunk+00000020
[ 57] 0x00007fffc1f63691                      C:\WINDOWS\SYSTEM32\ntdll.dll+00472721 RtlUserThreadStart+00000033


This error was detected while a MEX-file was running. If the MEX-file
is not an official MathWorks function, please examine its source code
for errors. Please consult the External Interfaces Guide for information
on debugging MEX-files.
** This crash report has been saved to disk as C:\Users\TANVIJ~1\AppData\Local\Temp\matlab_crash_dump.532-1 **


Caught MathWorks::System::FatalException
[Please exit and restart MATLAB]>> 



On Sunday, October 27, 2019 at 12:56:32 PM UTC-4, marianux wrote:
Try A, ir You have further issues, feel free yo ask.

Good luck
M

El dom., 27 de oct. de 2019 13:45, <tanvi....@gmail.com> escribió:
Thank you for your response! Which version of 2018 would you recommend, A or B?

On Sunday, October 27, 2019 at 12:37:47 PM UTC-4, tanvi....@gmail.com wrote:
Hello,

I am using Matlab version 2019B to run the ECG kit and am running into some problems while trying to run the examples. What is the best version to run this kit on?

--
You received this message because you are subscribed to the Google Groups "ecg-kit users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ecg-ki...@googlegroups.com.

Mariano Llamedo Soria

unread,
Oct 27, 2019, 11:11:54 PM10/27/19
to jta...@umich.edu, ecg-kit users
Hi, it is related to a compilation issue in your system of the aristotle QRS detector. Probably this problem with your compiler could cause other issues. Make sure that the installation script of the kit can compile all MEX sources. You can go to the part of the install script that executes the "mex" instruction, run it on your own, correct your problems, and once your compiler is ok, run the installation script again.

Best, 
M.



To unsubscribe from this group and stop receiving emails from it, send an email to ecg-kit-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ecg-kit-users/d4bac3f0-5ab0-4ee9-a7f1-3d9841be1982%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages