Hello,

I would like to ask about the IDataService.getOfflineTimeDomain(int shift) method.

I have used it to get the last two offline time domains (current and previous one - indexed 0 and -1). I found that the results are slightly different on local and remote strategy run.

On remote:


On local:


Could someone please explain what causes this differences? And do I have the guarantee that results on remote run will always be "rounded" to exact hour?

Code sample used to generate those resuls:

for (int i = 0; i > -2; i--) {
  ITimeDomain timeDomain = dataService.getOfflineTimeDomain(i);
  long start = timeDomain.getStart();
  long end = timeDomain.getEnd();
  context.getConsole().getOut().println("TimeDomain " + i + ": " + start + " (" + new Date(start) + ") - " + end + " (" + new Date(end) + ")");
}

Regards.

This is a bug on remote, we have registered this issue and are going to fix it as soon as possible.

Local run behavior is the correct one. Method ITimeDomain.getStart() returns the time of the last tick of trading week and ITimeDomain.getEnd() returns the time of the first tick of trading week in case of two last passed weekends. In all other cases (earlier than two last passed weekends or upcoming weekend) it should return Friday 21:00:00 UTC and Sun 21:00:00 UTC respectively (with corresponding dates).

Thank you for your answer.

Is IDataService.isOfflineTime() method based on the same values (real time in case of two last weekends and 21:00 UTC in other cases)?

Yes, it's logic should be the same.