Skip to content

Commit

Permalink
Re #7822. Keep the last log entries instead of clearing.
Browse files Browse the repository at this point in the history
The previous way presented problems with unchanging or
slowly varying logs as a chunk could be left with an empty
log that the analysis relied on having.
The particular problem one was 'EnergyRequest', which was
only appearing in the first chunk.
I think that we can count on the logs coming in in time order, so the
fact that the underlying methods don't check or sort should not be a
problem.
  • Loading branch information
RussellTaylor committed Oct 1, 2013
1 parent 685d147 commit 2dec716
Showing 1 changed file with 2 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -1239,8 +1239,8 @@ namespace LiveData
//Copy geometry over.
API::WorkspaceFactory::Instance().initializeFromParent(m_eventBuffer, temp, false);

// Clear out the old logs
temp->mutableRun().clearTimeSeriesLogs();
// Clear out the old logs, except for the most recent entry
temp->mutableRun().clearOutdatedTimeSeriesLogValues();

// Lock the mutex and swap the workspaces
{
Expand Down

0 comments on commit 2dec716

Please sign in to comment.