Milliseconds - Revision history

Mostow: /* Notes/Comments */

2011-12-13T23:04:15Z

Notes/Comments

← Older revision		Revision as of 23:04, 13 December 2011
Line 6:		Line 6:

	== Notes/Comments ==		== Notes/Comments ==
	* Jack Mostow needs ~~it too~~ in order to import Project LISTEN data. [[User:Mostow\|Mostow]] 23:00, 13 December 2011 (UTC)		* Jack Mostow needs milliseconds -- whether as part of time fields or in separate ms fields provided they get used -- in order to import Project LISTEN data, where differences of milliseconds in word reading time are meaningful. [[User:Mostow\|Mostow]] 23:00, 13 December 2011 (UTC)
	* Phil Pavlik has started asking for this.  Email 3/12/2008.  ET Mtg 4/9/2008.		* Phil Pavlik has started asking for this.  Email 3/12/2008.  ET Mtg 4/9/2008.
	* Connie Guan is asking for this too. 4/2008.		* Connie Guan is asking for this too. 4/2008.

Mostow: /* Notes/Comments */ Jack Mostow needs milliseconds to import Project LISTEN data.

2011-12-13T23:00:07Z

Notes/Comments: Jack Mostow needs milliseconds to import Project LISTEN data.

← Older revision		Revision as of 23:00, 13 December 2011
Line 6:		Line 6:

	== Notes/Comments ==		== Notes/Comments ==
			* Jack Mostow needs it too in order to import Project LISTEN data. [[User:Mostow\|Mostow]] 23:00, 13 December 2011 (UTC)
	* Phil Pavlik has started asking for this.  Email 3/12/2008.  ET Mtg 4/9/2008.		* Phil Pavlik has started asking for this.  Email 3/12/2008.  ET Mtg 4/9/2008.
	* Connie Guan is asking for this too. 4/2008.		* Connie Guan is asking for this too. 4/2008.

Alida at 18:46, 29 October 2010

2010-10-29T18:46:51Z

← Older revision		Revision as of 18:46, 29 October 2010
Line 12:		Line 12:
	** "I realize this is a very fine point, but we thought we'd mention it anyway: In E08E7-Jan24-10-04-23.xml there is a deletion event followed immediately by a hint request. Both these events occur within the same second, so carry the same time stamp to 1-second granularity: 2006-01-24 10:58:41.:In the exported log, it turns out the DELETION event is listed AFTER the hint request and before the hint response. This sequence is confusing to look at, because it suggests the student did something in the middle of the hint sequence, and that is not supposed to be possible on our interface. Because our logs are sequentially generated within a single thread of execution, we know the order of events in the logs corresponds to the order in which the events occurred in time, even if timestamps do not have sufficient granularity distinguish them. So it would be nice if that order could be preserved in the exported data."		** "I realize this is a very fine point, but we thought we'd mention it anyway: In E08E7-Jan24-10-04-23.xml there is a deletion event followed immediately by a hint request. Both these events occur within the same second, so carry the same time stamp to 1-second granularity: 2006-01-24 10:58:41.:In the exported log, it turns out the DELETION event is listed AFTER the hint request and before the hint response. This sequence is confusing to look at, because it suggests the student did something in the middle of the hint sequence, and that is not supposed to be possible on our interface. Because our logs are sequentially generated within a single thread of execution, we know the order of events in the logs corresponds to the order in which the events occurred in time, even if timestamps do not have sufficient granularity distinguish them. So it would be nice if that order could be preserved in the exported data."
	* Developer Note: Scarab Issue: DS65 Need to store microseconds in the action time stamps. [Aug 2005]		* Developer Note: Scarab Issue: DS65 Need to store microseconds in the action time stamps. [Aug 2005]


	<br>		<br>
	----		----
	See ~~complete~~ [[DataShop Feature Wish List]].		See completed [[DataShop 3.x Features]]<br>
			See on-going [[DataShop 4.x Features]]<br>
			See prioritized [[DataShop Feature Wish List]]<br>
			See unordered [[Collected User Requests]]
	[[Category:Protected]]		[[Category:Protected]]
	[[Category:DataShop]]		[[Category:DataShop]]
			[[Category:DataShop Feature]]

Alida at 14:23, 1 September 2009

2009-09-01T14:23:55Z

← Older revision		Revision as of 14:23, 1 September 2009
Line 18:		Line 18:
	See complete [[DataShop Feature Wish List]].		See complete [[DataShop Feature Wish List]].
	[[Category:Protected]]		[[Category:Protected]]
	[[Category:DataShop]		[[Category:DataShop]]

Alida: /* Notes/Comments */

2009-09-01T14:23:10Z

Notes/Comments

← Older revision		Revision as of 14:23, 1 September 2009
Line 6:		Line 6:

	== Notes/Comments ==		== Notes/Comments ==
	* Phil has started asking for this.  Email 3/12/2008.  ET Mtg 4/9/2008.		* Phil Pavlik has started asking for this.  Email 3/12/2008.  ET Mtg 4/9/2008.
	* Connie Guan is asking for this too. 4/2008.		* Connie Guan is asking for this too. 4/2008.
	* Previously asked for by Ying back in 2005 ~~(maybe what generated the scarab issue)~~.		* Previously asked for by Ying Liu back in 2005.
	* Maintain order of events which occur within same second. [Anders, email 10/3/2007]		* Maintain order of events which occur within same second. [Anders, email 10/3/2007]
	** "I realize this is a very fine point, but we thought we'd mention it anyway: In E08E7-Jan24-10-04-23.xml there is a deletion event followed immediately by a hint request. Both these events occur within the same second, so carry the same time stamp to 1-second granularity: 2006-01-24 10:58:41.:In the exported log, it turns out the DELETION event is listed AFTER the hint request and before the hint response. This sequence is confusing to look at, because it suggests the student did something in the middle of the hint sequence, and that is not supposed to be possible on our interface. Because our logs are sequentially generated within a single thread of execution, we know the order of events in the logs corresponds to the order in which the events occurred in time, even if timestamps do not have sufficient granularity distinguish them. So it would be nice if that order could be preserved in the exported data."		** "I realize this is a very fine point, but we thought we'd mention it anyway: In E08E7-Jan24-10-04-23.xml there is a deletion event followed immediately by a hint request. Both these events occur within the same second, so carry the same time stamp to 1-second granularity: 2006-01-24 10:58:41.:In the exported log, it turns out the DELETION event is listed AFTER the hint request and before the hint response. This sequence is confusing to look at, because it suggests the student did something in the middle of the hint sequence, and that is not supposed to be possible on our interface. Because our logs are sequentially generated within a single thread of execution, we know the order of events in the logs corresponds to the order in which the events occurred in time, even if timestamps do not have sufficient granularity distinguish them. So it would be nice if that order could be preserved in the exported data."
	* Developer Note: Scarab Issue: DS65 Need to store microseconds in the action time stamps.		* Developer Note: Scarab Issue: DS65 Need to store microseconds in the action time stamps. [Aug 2005]

Alida: New page: '''Status: Requirements Complete; Estimate Needed''' == User Story == As a researcher in a language domain, I want to see milliseconds in the timestamps, so that I can understand better ...

2009-09-01T14:21:57Z

New page: '''Status: Requirements Complete; Estimate Needed''' == User Story == As a researcher in a language domain, I want to see milliseconds in the timestamps, so that I can understand better ...

New page

'''Status: Requirements Complete; Estimate Needed'''

== User Story ==

As a researcher in a language domain, I want to see milliseconds in the timestamps, so that I can understand better where the subject is having some trouble and to get better order of events that occur within the same second.

== Notes/Comments ==
* Phil has started asking for this.  Email 3/12/2008.  ET Mtg 4/9/2008.
* Connie Guan is asking for this too. 4/2008.
* Previously asked for by Ying back in 2005 (maybe what generated the scarab issue).
* Maintain order of events which occur within same second. [Anders, email 10/3/2007]
** "I realize this is a very fine point, but we thought we'd mention it anyway: In E08E7-Jan24-10-04-23.xml there is a deletion event followed immediately by a hint request. Both these events occur within the same second, so carry the same time stamp to 1-second granularity: 2006-01-24 10:58:41.:In the exported log, it turns out the DELETION event is listed AFTER the hint request and before the hint response. This sequence is confusing to look at, because it suggests the student did something in the middle of the hint sequence, and that is not supposed to be possible on our interface. Because our logs are sequentially generated within a single thread of execution, we know the order of events in the logs corresponds to the order in which the events occurred in time, even if timestamps do not have sufficient granularity distinguish them. So it would be nice if that order could be preserved in the exported data."
* Developer Note: Scarab Issue: DS65 Need to store microseconds in the action time stamps.

<br>
----
See complete [[DataShop Feature Wish List]].
[[Category:Protected]]
[[Category:DataShop]