The past midnight, consecutive day recording bug is a reporting display issue that occurs in LENA Pro/Pilot/Grad software when the following criteria are both met:

1. Recording files are initiated on consecutive recording dates.
2. A recording from the first file extends past midnight into the next recording date.

The bug affects both data calculations and data presentation in the following outputs:

1. Report List view
2. Daily CSV export
3. LENA Core Reports viewed at the Daily level

In addition,presentation is affected in the following:

1. LENA Core Reports, Hourly
2. LENA Core Reports, 5-Minute

The bug does not affect processing, the ITS file itself, or export of the ITS, TRS, or CHA.

Midnight+Consecutive Effects on Report List, Daily CSV, Daily LENA Bar Graphs

In Report List, Daily CSV, and daily-level LENA bar graph roll-overs, the following effects are seen:

1. The filename displayed in Report List/CSV belongs to file initiated on Day 1, even if only a few seconds of its data were collected on Day 2.
2. If File 2 also extends past midnight into Day 3, its filename appears only for recording Day 3, where the duration and counts from only the Day 3 portion are displayed.
3. If File 2 does not extend past midnight but is fully contained within Day 2, its filename is not displayed at all in Report List or Daily CSV.
   • In this scenario, the incomplete Report List can lead to confusion when reprocessing due to misassignment or a date of birth error. Further, the daily CSV would not contain some of the file assignment informationnecessary for a database merge.
4. The duration/recorded hours value displayed for Day 2 is the sum of the Day 2 portion of File 1 plus the Day 2 portion of File 2.
5. Actual counts/Actual recorded values for Day 2 are sums of all countson that day, from both files.
6. 12-Hour projection values, where applicable, are calculated from the summed Day 2 counts.
   • If File 1 runs past midnight by a small amount, the effect on projected counts and %iles is minimal.
   • If the Day 2 portion of File 1 contains several hours of 0 counts, the projected counts will be skewed downward.
   • Note: Report List shows only projected counts if the recording >/=10 hours, and only actual counts if <10 hours, without overtly specifying which.

Midnight+Consecutive Effects on Hourly/5-Minute CSVs and Hourly/5-Minute LENA Bar Graphs

Presentation is affected; calculations are not.

Hourly/5-Minute CSVs:

• The CSV Hourly/5-Min for Day 2 will include rows for Day 2 portions of both File 1 and File 2.
  • To work with data from File 2 only, the user must attend to the filenames and delete/ignore the irrelevant File 1 rows.

Hourly/5-Minute LENA bar graphs:

• Same effect as for the CSV, but visual/graphic. Bars will be displayed on Day 2 for File 1 and File 2, with a gap in between.

Current Remedies

The following options can help customers avoid the bug or lessen its impact on data analysis:

1. Avoid consecutive day recordings
2. Ensure that recordings always end before midnight
3. Assign one of the recordings to a second instance of the same child
   • Not an option for most LENA Pro Grad users due to limit of 25 participants
   • Users already affected can use ADEX/Excel to quickly identify recordings that need to be reassigned
   • Data for the child could be re-consolidated in exports
4. Use the ITS file export as the primary data source, avoiding the CSV

The following should be taken into account during support activities that rely on Report List and Daily CSV:

1. When reassigning files in preparation for reprocessing,check for the appearance of an additional file (hidden Day 2 file)in report list after each file is reassigned.
2. When preparing for a database merge, export the Hourly CSV (instead of daily) for file assignment information on hidden files.