Super pi days
-
Yes, yyyymmdd is the easiest to sort (date treated as an integer number) and mmddyyyy or ddmmyyyy is much more difficult :sigh: - In a Genealogy course I took in college we were told to write dates at dd-MMM-yyyy so there is no ambiguity :thumbsup: ... but then us Math guys are notorious for fiddling with the digits to get the desired results ;)
Steve _________________ I C(++) therefore I am
Read the discussions on date micro formats for HTML5 (sorry, I haven't got a link - I am sure that another CPian will be able to find some). Genealogies is cited as a difficult case as the dates go before 1752. The recommendation (in the microformats discussions) is that you still use the Gregorian dates, but that would be very confusing as the historical dates were Julian (which I am sure is what most genealogy courses would use). Also, genealogies hit one of the other date format 'gotchas': approximations; how do you represent 'sometime probably in September between 4BC and 1AD'?
-
In my workplace, we use yyyymmdd for comments, file naming, etc.. it's damn easy to sort. I have always felt that mmddyy is just irrational. You don't say a player finished a race in 23 mins 45 secs 1 hour. That's just ridiculous.
Peace, ye fat guts!
krumia wrote:
You don't say a player finished a race in 23 mins 45 secs 1 hour
No you don't. But it is more common to say "It is ten past eleven", than to say "It is 11 o'clock plus ten minutes". Admittedly, "It is 11:10" is quicker. Posted just after ten past eleven, GMT.
-
In just a few years we will have: 3/14/15 9:26:53.58 and 16 years later: 31/4/15 9:26:53.58 - which in the US will also be Income Taxes due Day X|
Steve _________________ I C(++) therefore I am
Pi is Wrong! :) Couldn't resist...
-
In just a few years we will have: 3/14/15 9:26:53.58 and 16 years later: 31/4/15 9:26:53.58 - which in the US will also be Income Taxes due Day X|
Steve _________________ I C(++) therefore I am
-
In just a few years we will have: 3/14/15 9:26:53.58 and 16 years later: 31/4/15 9:26:53.58 - which in the US will also be Income Taxes due Day X|
Steve _________________ I C(++) therefore I am
07/20/2069 19:37:33 will be unix timestamp 3141592653 other notable timestamps: time of the beast (unix timestamp 666) was 12/31/1969 19:11:06 Euler time (unix timestamp 2718281828) will be 02/20/2056 09:17:08 AM avagadro's time overflows a 64 bit int... so don't hold your breath and PHI time (unix timestamp 1618033988) is 04/10/2021 01:53:08 AM
-
Read the discussions on date micro formats for HTML5 (sorry, I haven't got a link - I am sure that another CPian will be able to find some). Genealogies is cited as a difficult case as the dates go before 1752. The recommendation (in the microformats discussions) is that you still use the Gregorian dates, but that would be very confusing as the historical dates were Julian (which I am sure is what most genealogy courses would use). Also, genealogies hit one of the other date format 'gotchas': approximations; how do you represent 'sometime probably in September between 4BC and 1AD'?
I first convert the Gregorian date to the Julian Day Count, make the calculated adjustment, then convert back to the Gregorian or Julian calendar. While this may seem an extra step in the process, it does have two advantages. 1. The dates remain in their numerical sequence and thus allow for accurate sorting. 2. Regardless of the calendar you convert back to, Gregorian or Julian, the date will be accurate within a 12 hour period. The one draw back to the JDC is that the JDC changes at noon rather than midnight. This could be rectified by creating a new day count that starts at midnight rather than noon. Scott A. Tovey
-
Obviously this only occurs in the US, in Europe with dd/mm/yy we get any early pi on March the 14th in 2015 So guess you have to refer to 3/14/15 as American pie :)
Bob1000 wrote:
Obviously this only occurs in the US, in Europe with dd/mm/yy
we get any early pi on March the 14th in 2015
So guess you have to refer to 3/14/15 as American pieHere in the US, most of us grow up using the dd/mm/yy format. The only ones who use that other format are the ones who need people to think that they are smart. They're insecure because of the increasing forgetfulness that they have been experiencing. Do you think we should tell them that's called "getting old"? Just one thing: What were we talking about? :laugh: Scott
-
In just a few years we will have: 3/14/15 9:26:53.58 and 16 years later: 31/4/15 9:26:53.58 - which in the US will also be Income Taxes due Day X|
Steve _________________ I C(++) therefore I am
More importantly, will τ be what is taught in schools by 6/28/31 8:53:07.179586... (in that crazy US date system) http://tauday.com[^]
-
In just a few years we will have: 3/14/15 9:26:53.58 and 16 years later: 31/4/15 9:26:53.58 - which in the US will also be Income Taxes due Day X|
Steve _________________ I C(++) therefore I am
In a few years, maybe we will get ticks in 1 tick increments, but right now, you're SOL if you are using SQL, but my C# apps can calculate in millisecond increments now, so the number can be one more digit long right now. What is interesting is PI shows up twice in the same year about a month and a half apart. (Yes, your format switch and 16 years difference did throw me at first too. A different format switch gets the month and a half) Also, that's 16 years, 1 month, and 1 day later. So, is the next PI series some 1129+ years from now? (What am I THINKING! It's only 100 years away from these numbers again! What I was first thinking was that a 4 digit year gets 2 places more in accuracy. 3141/5/9... twice for m/d and d/m formats.) Is there some C# option that tells datetime to increment in approximately 10,000 tick increments now? Can that be set differently?
-
krumia wrote:
You don't say a player finished a race in 23 mins 45 secs 1 hour
No you don't. But it is more common to say "It is ten past eleven", than to say "It is 11 o'clock plus ten minutes". Admittedly, "It is 11:10" is quicker. Posted just after ten past eleven, GMT.
Quote:
But it is more common to say "It is ten past eleven"
It's more common easy for verbal communication. The point is, most of the people admit that ddmmyy format is quicker/easier than mmddyy. But can anyone point out the advantage of mmddyy over ddmmyy?
Peace, ye fat guts!
-
I wonder why we just not count the days, how difficult it may be? For example today is 734456 AD. And of course the negative numbers will represent BC.
There is only one Vera Farmiga and Salma Hayek is her prophet! Advertise here – minimum three posts per day are guaranteed.
MMM, I think we need a more absolute time scale - starting from the beginning of the universe. But we can't forget that the time-scale units must include constant-less conversion into units of furlongs per fortnight and of course referenced to the speed of light. Something like 1 tick = pi*D/C where "D" is the current radius of the universe in parsecs and "C" is the speed of light expressed in furlongs/fortnight. Using a time-scale such as this should simplify both web programming and the math in a unified field theory.
-
In just a few years we will have: 3/14/15 9:26:53.58 and 16 years later: 31/4/15 9:26:53.58 - which in the US will also be Income Taxes due Day X|
Steve _________________ I C(++) therefore I am