Beyond the annotation'style, was good my idea of annotate the times with a
grid? each one press enter the cursor should be the next time stamp to edit
it.
This week I wrote the timestamps from my game played few days ago. The
process is so long and borig that I left the rest of my games to find
another way to analyze my times for the moment (maybe with gnumeric).
Regards
Esteban
2011/7/25 Alexander Wagner <aw-li...@stellarcom.org>
> On 07/19/11 19:17, Esteban Cervetto wrote:
>
> Hi!
>
> is it possible annotate in PGN standads the time issued per move?
>>> It is an important data when you have to analize your performance.
>>>
>>> I agree.
>>> I like the ICC format, just a comment with the remaining time (
>>> h:mm:ss )
>>> For example:
>>>
>>
>> 1. e4 {1:40:30} c6 {1:40:25} 2. d4 {1:40:02} d5 {1:40:50}
>>
>> I don't have time for scid development now, but after the summer i
>> will write some code to interpret a comment starting with h:mm:ss as
>> clock values and show it on the right of the board.
>>
>> Great! It would be remarkable keep in mind that some points and
>> ideas before begin to write code:
>>
>> 1) Usually, the reflection time per game doesn't last more
>> than 120 minutes. In my personal games, I only wrote the total
>> minutes expended.
>>
>
> You're only considering OTB gameplay here. One should
> howerver strive for a general solution to the issue. Also
> note that there's also another AFAIK estabilished form of
> time notation, something linke
>
> [%ccsnt 2011.06.16,17:53]
>
> (This is CC gameplay, therefore the date matters as well.)
>
> Nevertheless, it might be wise to check out [% ] notations.
> Especially, considering that it's perfectly simple to hide
> those annotations and avoid crowding PGN notation. (Just
> switch off arrow marks.)
>
> AFAIK it is common to use [%ct ] and [%emt ] for usual game
> times. Note that this is also the way input engine stores
> times if timing is provided. It might also be worth while to
> check what some larger commercial company uses as
> commentaries for time storage. (I think it's the above but
> I'm not 100% sure about it.)
>
>
> 2) Annotate time for all the moves is a very boring task.
>>
>
> One should keep in mind that in real game play you might
> already get the time stamps from a digital clock or, in
> Scids game play functions by the internal clock.
>
> For external time sources input engine comes to mind again,
> e.g. I store timings from a DGT clock right into the
> notation. The format used by Scid is
>
> [%ct $wHrs:$wMin:$wSec] [%emt $timediff]
>
> --
>
> Kind regards, / War is Peace.
> | Freedom is Slavery.
> Alexander Wagner | Ignorance is Strength.
> |
> | Theory : G. Orwell, "1984"
> / In practice: USA, since 2001
>
------------------------------------------------------------------------------
Magic Quadrant for Content-Aware Data Loss Prevention
Research study explores the data loss prevention market. Includes in-depth
analysis on the changes within the DLP market, and the criteria used to
evaluate the strengths and weaknesses of these DLP solutions.
http://www.accelacomm.com/jaw/sfnl/114/51385063/
_______________________________________________
Scid-users mailing list
Scid-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scid-users
