Problems encountered will using this toolbox, rdsamp related

[Meri Gjika]

While using rdsamp function of this toolbox, we encountered few times the following problem linked with the reading of .dat files. The error message was the following:

Error using rdsamp

Could not find record: C:\Users \Documents\mcode\database\02012. Search path is set to: '.

C:\Users\Documents\mcode\..\database\http://physionet.org/physiobank/database/'

It is an error linked to the search of the record, even though the toolbox was correctly installed, and the file existed in the specific path, MATLAB still displayed the error.We observed that this issue tended to occur after the function had not been used for a certain period or when it was executed from a different MATLAB script within the same folder.

Another issue we encountered was related to Java, in specific the toolbox was not able to locate the necessary Java class, giving the following error as output:

Unable to resolve the name

'org.physionet.wfdb.Wfdbexec'.

Error in getWfdbClass

javaWfdbExec=javaObject('org.physionet.wfdb.Wfdbexec',commandName,config.WFDB_CUSTOMLIB);

Error in rdsamp

[javaWfdbExec,config]=getWfdbClass('rdsamp');

Error in getWfdbClass

[~,config]=wfdbloadlib;

In this case the approach we followed was to verify that the correct Java version was present and ensure that there were no errors within Java itself. However, the problem persisted. Like the previous issue, it occurred after a period of inactivity or when rdsamp was executed from a different MATLAB script.After numerous attempts to resolve the issue, we ultimately fixed it by uninstalling and reinstalling the toolbox—a process that was understandably time-consuming.

These challenges affect the function's reliability and ease of use, particularly when working with .dat files. Enhancing configuration persistence between sessions and offering a more transparent debugging system would improve the toolbox, reducing the need for frequent reinstalls.