File Synch problem with timestamp

[Dynamik]

Hi CoastalMainBird,

      I don't know if this helps solve the original problem, but It looks like LabVIEW rounds-up seconds when reporting times - and the Properties-dialog doesn't.

Also, here's a quickie util for getting a more accurate file-system time (from Windows).

[CoastalMaineBird]

I don't know if this helps solve the original problem, but It looks like LabVIEW rounds-up seconds when reporting times - and the Properties-dialog doesn't.

Well, even if that were true (which I don't think it is) it still doesn't explain BOTH issues - 1) why LV shows different time than Properties, and 2) why LV reports different time on server than on local.

Also, here's a quickie util for getting a more accurate file-system time (from Windows).

THANKS!

I just ran a test on one of the files that "fails" my synch logic - here are the results: The SOURCE is the local drive (C: ), the DEST is the remote drive (R: ).

METHOD               SOURCE TIME                DEST TIME
Properties      5/26/2006  9:43:39 AM    5/26/2006  9:43:39 AM
LV File Info    5/26/2006  9:43:40.21    5/26/2006  9:43:39.21     <--- 1.0 sec difference!
Util.File.Time  12793124619.53125        12793124619.00000         <--- 0.53125 sec difference!

From this, I notice that the remote time has been truncated, not rounded. That is probably the source of the problem. It might have something to do with it being a remote system, or it being an OS X file system.

My guess is that the properties dialog does the truncation as well, which is why it shows the same time for both ends. LabVIEW's FILE INFO function apparently rounds to the nearest second (where the "0.21" comes from, I don't know - last week, it was 0.17 for all files). Your utility does neither. Thanks for your thoughts!

I believe I'll stick with the 2-sec "tolerance", as it's cross-platform, and possibly faster, but I do appreciate knowing the source of the issue.

[Dynamik]

Hi CMB,

      I'm not sure you understand the suggestion "It looks like LabVIEW rounds-up seconds when reporting times - and the Properties-dialog doesn't."  (Also note picture attached showing seconds-descrepancy for the file named "mmdet.log".  accurate sec. ~3.53, LabVIEW sec. ends in 4, Properties ends in 3 )

The reply "Well, even if that were true (which I don't think it is)" - ignores the picture-evidence

> My guess is that the properties dialog does the truncation as well, which is why it shows the same time for both ends.

> LabVIEW's FILE INFO function apparently rounds to the nearest second

Nice observation!

> My guess is that the properties dialog does the truncation ... FILE INFO function apparently rounds to the nearest second ... Your utility does neither.

Well, this is a good thing, right? (having provided an unobstructed view of the details?)

Glad you've got a handle on the issue - it was an interesting puzzler!

[CoastalMaineBird]

I'm not sure you understand the suggestion "It looks like LabVIEW rounds-up seconds when reporting times - and the Properties-dialog doesn't." (Also note picture attached showing seconds-descrepancy for the file named "mmdet.log". accurate sec. ~3.53, LabVIEW sec. ends in 4, Properties ends in 3

I was distinguishing between "rounds up" as you said, and "rounds to nearest" as LV apparently does. They are different functions, in my mind (as well as on the LV palette).

> My guess is that the properties dialog does the truncation ... FILE INFO function apparently rounds to the nearest second ... Your utility does neither.
Well, this is a good thing, right? (having provided an unobstructed view of the details?)

Certainly - I didn't mean any negative connotation by the "does neither" phrase - it sure is a good thing! Perhaps a poor choice of words on my part.

Anyway, thanks for the stimulus. That made it obvious that somebody is truncating the time to the nearest second, and somebody else is not.

Message Edited by CoastalMaineBird on 06-06-2006 06:18 PM

[Dynamik]

> I was distinguishing between "rounds up" as you said, and "rounds to nearest"

Oh jeeze, right you were. Hey, thanks for the clarification!