Why do you want to use ASCII? If you are designing the project, you don't need
to use ASCII format. Avoid ASCII and stick with EDF.
If you insist, the easiest way is to modify this EDF to ASCII converter:
http://www.teuniz.net/edf2ascii/
Otherwise use EDFlib to write a single channel EDF to ASCII converter:
http://www.teuniz.net/edflib/
Anyway, you need some C-programming skills or find somebody who can do this for
you.
Best regards,
Teunis van Beelen
Hi,
I'm a student at the University of Toronto studying Electrical Engineering and
Biomedical Engineering. I'm working on a project to design an artificial neural
net that will be able to recognize sleep states based on EEG data. I have a
large (1000) set of EDF files from the PsysioRepository that have 14 signals
each (EEG, EKG, EOG, etc...). I'm looking to extract only the EEG data in ASCII
format from the files. I've found some great programs out there that can do this
from a GUI one at a time but I would ideally like to do this via script (PERL
etc...) so I can automate the process. The only programs I've found that can do
this extract all 14 signals which creates massive files (50Mb EDF -> 5 Gb ASCII)
I was wondering if anyone here had a method of batch extracting and converting a
single signal from an EDF file.
Thanks for any help you can give,
David
To whom it may concern,
I published an opensource ADC-box project at
http://www.teuniz.net/12-ch_ADC-board/
that exports EDF+.
Best regards,
Teunis van Beelen
EDFlib now supports reading and writing EDF+/BDF+ files.
Reading/writing EDF+ files (including annotations) is a breeze with this
library.
I provided a precompiled windows DLL as well.
http://www.teuniz.net/edflib/
Regards,
Teunis van beelen
Thanks Howard,
I will correct this in the next version.
Next version will write files as well.
I will also provide a DLL of EDFlib.
--- In EDF@yahoogroups.com, "howardlightstone" <howard@...> wrote:
>
> --- In EDF@yahoogroups.com, "teunizz" <teuniz@> wrote:
>
> >
> > Maybe somebody can test it with ms visual c compiler?
> >
> > Let me know if there are any questions, suggestions, problems, difficulties,
whatever.
>
> Tested with Visual Studio 2005 with some issues:
> 1. Stupid compiler doesn't like inline declarations NOT in a block so I moved
them above the first executable lines. This should still work with all the
compilers.
>
> 2. Some sizeof logic didn't work so I restated them (hopefully correctly).
>
> After some changes, it looks like it reads just fine. I'll try to make a
Python .pyd that can be used (but only if some 'spare time' miraculously
appears).
>