Hello Guest, Welcome to Apnea Board !
As a guest, you are limited to certain areas of the board and there are some features you can't use.
To post a message, you must create a free account using a valid email address.

or Create an Account

New Posts   Today's Posts

ID's and work arounds for CSV importing and other general software problems
ID's and work arounds for CSV importing and other general software problems
This thread is intended to be helpful to members as a repository for contributions of all our proven methods of dealing with general software brick walls we encounter. As individuals, many of us with limited programming skills, deal with sleep apnea related data import, export and analysis difficulties, especially when first using other common or device supporting software tools.

Suggestion: Other specific program difficulties encountered in, say, a member's use of OSCAR or, say, an oximeter, would likely get faster responses from posting that person's own specific thread and calling for help. After resolution of a problem using forum help, it can be helpful to others--as I hope I will be now with this thread and first post--if you post in this thread a brief description of your problem, how it was solved, make use of any key words (for others' AB or google searches), and provide a link to your thread for all the detail. That way your amazing solution, not always well described by my (your?) thread's chosen subject, will not get buried in a thread that will disappear over the forum's time horizon, never to be found again except by clever searching.

Here's a kick off with my general software (CSV) handling problem and its solution: 

I got a Dreem headband that provided sleep stage data in a CSV file. My first few imports worked perfectly, but the CSV data needed to be cleaned up due to my poor workflow and time management as a fumbling newbie.  

After a few successful imports of Dreem CSV data file, as-is, into OSCAR, I decided to edit that data and do clean up edits. After doing so using Excel, OSCAR imports would indicate data had been imported but there were never any detailed graphs being generate to show sleep stages through the night. 

It turned out, thanks to Crimson Nape (primarily) and others' helps, that the Excel version of a CSV file differs from the Dreem CSV file in how detailed data lines end. Oscar was seeing Excel's invisible CRLF  (carriage return ASCII 13 with LF line feed ASCII 10) at the ends of all data lines of the Excel opened (and thereby blighted) CSV file. OSCAR refused it, demanding that there only be the LF that proper Dreem CSV data rows do present. 

The childishly simple solution was simply to use NotePad++, but not NotePad, to open, edit and save the dreem_export.csv file as a CSV file. Then, import that NotePad++ CSV file into OSCAR.  

(Along my tortuous path, I learned that the "debug log" listing item, accessible through OSCAR's Data-Advanced-Troubleshooting menu choice sequence, presents a way to expose the debug log which, I learned, traces/summarizes the internal program path that OSCAR used in setting up my immediate OSCAR session for view on screen. Not knowing much, now or then, I could at least see there that summary files for Dreem data had been prepared, but not the details files, nor their Events file holder. All this could be sniffed out, even by this software newbie, eventually, after checking matters via OSCAR's app data folder in the Documents folder. By that path I came to see the needed Dreem profile alongside my VAuto's profile, along with a Dreem Summary folder and without the missing Events folder that should have held Dreem sleep stage data. All of this was and still is almost totally Greek to me.)

A link to my struggle thread if you want to see gory details: http://www.apneaboard.com/forums/Thread-...lp-request

Here are other links to some of the related sites I visited when groping for info, hints and solutions. Note that one site, possibly linked below, indicated there are even various hidden differences among UTF-8 code page outputs and inputs, a matter I looked at not knowing what was wrong at the time.). I suffered no known virus consequences and learned a lot from such reading, but the breakthrough came from Crimson Nape putting his finger on the CRLF problem, and then my using NotePad++ to see the hidden CRLF's at ends of rows, using NotePad++. Then I could to edit Dreem csv files in NotePad++, if needed, do saves with it to CSV and then do imports of the NotePad++ digested file into OSCAR.

Solved: UTF-8 CSV output without BOM? - Alteryx Community
Saving CSV/Excel file as UTF-8 Encoded – WooCommerce Product Import Export - WebToffee

Google search: utc-8 utc-16 bom eom excel csv

Good luck finding your problem's general software solution. I hope you find and will post a summary of your findings and a link to your solution thread here.

Post Reply Post Reply

Donate to Apnea Board  

Possibly Related Threads...
Thread Author Replies Views Last Post
  problems with software Oscar [resolved, see post #2] Alessandro 3 119 01-20-2021, 05:15 AM
Last Post: Alessandro
  OSCAR: Synchronization -- general question PurchanceToDream 5 102 01-19-2021, 03:19 AM
Last Post: PurchanceToDream
  Importing SleepU Data in OSCAR -- can't find AppData folder PurchanceToDream 4 75 01-15-2021, 01:52 AM
Last Post: PurchanceToDream
  Dreem 2 to OSCAR importing help request 2SleepBetta 18 627 12-12-2020, 01:07 AM
Last Post: 2SleepBetta
  Prisma TS software malfadors 9 1,374 12-08-2020, 09:45 AM
Last Post: wolvieh
  Why do day numbers turn from blue to red after importing SpO2 data into OSCAR? epc002 1 129 11-27-2020, 11:36 AM
Last Post: GuyScharf
  software not working fortopman 1 216 11-25-2020, 08:58 PM
Last Post: GuyScharf

New Posts   Today's Posts

About Apnea Board

Apnea Board is an educational web site designed to empower Sleep Apnea patients.