wfdb-app-toolbox icon indicating copy to clipboard operation
wfdb-app-toolbox copied to clipboard

Offline usage does not work

Open GoogleCodeExporter opened this issue 9 years ago • 4 comments

What steps will reproduce the problem?
1. Internet connectivity
2. Working Matlab Code which uses wfdb functions (e.g. wfdbdesc on a local file)
3. physionet.org has some server problem and can not be accessed.  

What is the expected output? What do you see instead?
dead loop in wfdbdesc

What version of the product are you using? On what operating system?
Ubuntu 12.04 3.11.0-23-generic # x86_64, 
Matlab 7.14.0.739 (R2012a)
WFDB Toolbox 0.9.6.1

Please provide any additional information below.
Ctr-C does not work any more. Force close of Matlab

Original issue reported on code.google.com by [email protected] on 12 Jun 2014 at 6:36

GoogleCodeExporter avatar Mar 13 '15 23:03 GoogleCodeExporter

On Windows 7 with Matlab R2013b it takes about 3 min till siginfo and fs is 
returned

Original comment by [email protected] on 12 Jun 2014 at 6:41

GoogleCodeExporter avatar Mar 13 '15 23:03 GoogleCodeExporter

With no internet connectivity, results are available immediately, as expected.

Original comment by [email protected] on 12 Jun 2014 at 6:42

GoogleCodeExporter avatar Mar 13 '15 23:03 GoogleCodeExporter

Was able to reproduce in a Mac as well (both with RDSAMP and WFDBDESC):

[~,config]=wfdbloadlib;
cd([config.WFDB_JAVA_HOME(2:end) 'example'])
[siginfo,fs]=wfdbdesc('100a.hea')

Yields empty results, but calling from WFDBEXEC it works:

wfdbexec('wfdbdesc',{'100a'})

ans = 

    'Record 100a'
    'Notes'
    '====='
    ' From mitdb/100'
    '====='
    ''
    'Starting time: not specified'
    'Length:    30:05.556 (650000 sample intervals)'
    'Sampling frequency: 360 Hz'
    '0 signals'

Original comment by [email protected] on 19 Jun 2014 at 4:02

  • Changed state: Accepted
  • Added labels: Priority-Critical
  • Removed labels: Priority-High

GoogleCodeExporter avatar Mar 13 '15 23:03 GoogleCodeExporter

A user reported a possible work-around by using WFDB2MAT and RDMAT together 
instead of RDSAMP. This seems to be problem specific to RDSAMP and WFDBDESC.

Original comment by [email protected] on 21 Nov 2014 at 9:39

GoogleCodeExporter avatar Mar 13 '15 23:03 GoogleCodeExporter