53

The short answer is, yes! There is a whole undocumented package TemporalData` containing some useful functions. The results below are from my own spelunking. Feel free to add/amend as appropriate. Let's set up some simple TemporalData objects to explore them: fakedata = Transpose@{DatePlus[{2001, 1}, {#, "Month"}] & /@ Range[0, 99], ...


38

It took me quite a while, but finally, here's a visualization of the perigee of Flamsteed's comet: I should first note two things: first, some of the needed data for computing the orbit of comet C/1683 O1 was missing in AstronomicalData["CometC1683O1", "Properties"], and I had to pull information from external sources to supplement the information available;...


38

Indeed, this functionality still exists, but it has been moved into its own package. Load the package: Needs["aBetterProgrammer`"] You will have access to such functions as GimmeDaCodez (answers any nebulous MMA.SE question by guessing the unspoken needs of the asker) WizardForm (an output wrapper; produces perfectly terse code; all function calls are ...


37

Date-picker implementation in Mathematica The following is my implementation of a simple date-picker. The current date is highlighted in LightBlue and the weekends are highlighted in LightGreen. The selected date is always highlighted in LightRed (the default selection is the current date). You can tap into this calendar by using the Dynamic values for ...


25

Just a literal implementation of a formula for the day of the week: Clear[dow]; dow[{year_, month_, day_, _ : 0, _ : 0, _ : 0}] := Module[{Y = If[month == 1 || month == 2, year - 1, year], m = Mod[month + 9, 12] + 1, y, c, s = {Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday}}, y = Mod[Y, 100]; c = Quotient[Y, 100]; s[[...


23

Since version 11 most commands finally support the Interpretation option: Interpretation -> "Literal" being the classical (default) way of operation, and Interpretation -> "Guess" using advanced machine learning to get much better results than ReadProgrammerIntentions ever achieved. Makes programming a lot easier. You can emulate the old behavior with ...


22

I will provide one solution which will be using Java and a simple Java reloader I recently introduced. This solution brings to the table up to 100-fold speed-up for large lists of dates. Preparation I will borrow @Mike's functions to generate a random list of dates, from his code in his recent question RandomDateList[] := { RandomInteger[{1800, 2100}], ...


20

I tried to do something similar a few months ago The easiest way is to write several functions: EventFrame function creates event lables EventFrame[str_, {date_, height_}, OptionsPattern[FontSize -> 14]] := Graphics[{ Black, Thick, Line[{{date, height}, {date, 0}}], Text[Framed[Style[str, FontSize -> OptionValue[FontSize]], {Background -> ...


20

This site has exactly what you want here, already in Mathematica code. One example here:


20

I tend to use a pattern matching approach: myCode/.{x_?BugQ:>BugStrip[x],x_?TypoQ:>Detypo[x],x_?WrongSignQ:>-x,x_?OffBy2PiQ:>x*2\[Pi]} With the usual caveat that pattern matching can be slower than other methods, but conceptually easier to understand. Hopefully someone will aggregate the answers to compare performance. Good luck!


19

There is a built-in DateSetter: {Developer`DateSetter[Dynamic@date], Dynamic@date} By default the first selectable date is tomorrow and one can only go to future months. However, the option NotebookTools`DateSetterRange can be used to set the first selectable date to sometime in the past, {Developer`DateSetter[Dynamic@date, NotebookTools`DateSetterRange -&...


18

Since I'm living in Europe I'm sticking to the European definition of week number which is equivalent to the ISO standard. According to this standard, a week starts on Monday and the first week is the week containing 4 January. Taking this into account you could do therefore do something like weekNumberISO[date_] := Module[{day0, year}, With[{days = {"Mon"...


18

This function was deprecated in V4.2, being succeeded by CellularAutomaton. Since your answer is hidden somewhere in rules like 110, why reinvent the wheel with ReadProgrammerIntentions?


17

You can use DateDifference to find the time between January 1st and April 17th: DateDifference["Jan. 1", "April 17", "Week"] (* {15.2857, "Week"} *) If you want the "week number" as you've put it, you can just do: Ceiling@First@DateDifference["Jan. 1", "April 17", "Week"] which gives 16. Edit based on Szabolcs's comment: To ensure this works for Jan 1.,...


16

The format specification for DateList is pretty flexible. Since we know that we have <h3> tags wrapped around things, we can just account for them: DateList[{#, {"<h3>", "MonthName", "Day", ",", "Year", "</h3>"}}] & /@ Flatten[dates] (* ==> {{2001, 1, 18, 0, 0, 0.}, {2001, 2, 1, 0, 0, 0.}, {2001, 2, 2, 0, 0, 0.}, {2001, 2, 24,...


16

The reason for the result of DateDifference[{2015, 4, 1}, {2015, 10, 1}, "Year"] (* Quantity[0.5, "Years"] *) is that 2016 is a leap year, so there are 366 days in the year between {2015, 4, 1} and {2016, 4, 1}. Therefore we get 183/366 or exactly 1/2 back. Note also the documented DayCountConvention option, DateDifference[{2015, 4, 1}, {2015, 10, 1}, "...


15

Building off the other answer, CountryData has the data for the time zones for each country, as well as their population. So we can split each country proportionally into its individual timezones: countries = CountryData[]; populations = CountryData[#, "Population"] & /@ countries; timeZones = CountryData[#, "TimeZones"] & /@ countries; data = ...


14

As of Mathematica 10.1, creating a timeline is built-in with TimelinePlot[]. TimelinePlot[{ Labeled[Interval[{DateObject[{2010, 2, 1}], DateObject[{2013, 5, 4}]}], "label1"], Labeled[DateObject[{2012, 4, 6}], "label2"], Labeled[Interval[{DateObject[{2011, 3, 1}], DateObject[{2012, 12, 21}]}], "label3"] }] Lots of possibilities, looking at ...


14

Jean Meeus's Astronomical Algorithms (as well as the related book Astronomical Formulæ for Calculators) is what you should start looking at whenever you need to deal with algorithms for quantities of astronomical interest. For instance, here is a translation of Meeus's method for the Julian Date: Options[jd] = {"Calendar" -> "Gregorian"}; jd[{...


14

So this generates the heatmap: << Calendar` year = 1990; yearLen = DaysBetween[{year, 1, 1}, {year, 12, 31}] + 1; data = RandomReal[1, yearLen]; days = Map[DayOfWeek[{year, 1, #}] &, Range[3, 9]]; day1 = Position[days, DayOfWeek[{year, 1, 1}]][[1, 1]]; dayn = Position[days, DayOfWeek[{year, 12, 1}]][[1, 1]]; Paddata = Join[ConstantArray[100, day1 -...


14

I would do this with rule replacement. First, you want to have a list of the days of the week in the appropriate order: days = DayName@{0, 0, #} & /@ Range[5, 11]; Then, you can take tallied results and turn them into a list of rules: tallied = {{Tuesday, 533}, {Sunday, 487}, {Saturday, 481}, {Friday, 422}, {Thursday, 353}, {Wednesday, 371}}; ...


14

For full ranges There is the function DayRange that can be used for this purpose, but not in the same simple way like CharacterRange. For the days: DayName /@ DayRange[Today, Today ~DatePlus~ {{1, "Week"}, {-1, "Day"}}] {Wednesday, Thursday, Friday, Saturday, Sunday, Monday, Tuesday} For the months: DateValue[#, "MonthName"] & /@ DayRange[Today, ...


14

This is how you can get the last 30 weekdays starting from yesterday: days = DayRange[DayPlus[Yesterday, -30], Yesterday, "Weekday"] To get {y,m,d} vectors, we might use Take[#, 3] &@*DateList /@ days Regarding the time zone, the only problem I can see would be that Yesterday will not produce the right result around midnight. To check this I used the ...


14

Instead of FindFit[], DistributionFitTest[] is the function to use to test the distribution followed by your data. Using easter[] from this answer, generate the number of days Easter is counted from March 23 of that same year: data = Table[DayCount[DateObject[{k, 3, 23}], DateObject[easter[k]]], {k, 1700, 2018}]; Then, hh = DistributionFitTest[data // N, ...


13

Import[(* file *), "Table", "DateStringFormat" -> {"Year", "-", "Month", "-", "Day"}] seems to work... As a test: Export["test.dat", {{"2010-05-19", 17}, {"2010-05-20", 20}, {"2010-05-21", 19}}, "FieldSeparators" -> " "]; Import["test.dat", "Table", "DateStringFormat" -> {"Year", "-", "Month", "-", "Day"}] {{{2010, 5, 19}, 17}...


13

Using Simon's data: In[6]:= datelist = {"29/02/2008", "15/12/2007", "06/09/2007", "06/10/2008", "05/03/2007", "24/01/2010", "19/06/2009", "03/11/2009", "02/02/2010", "25/12/2009"}; We can just sort the data by the absolute time: In[7]:= SortBy[datelist, AbsoluteTime[{#, {"Day", "Month", "Year"}}] &] Out[7]= {"05/03/2007", "06/09/2007", "15/12/...


13

For those with v. 10, here's one way. I didn't overlap the bars because it looks nicer this way, imho. schedule[{t1_, t2_}, {t3_, t4_}] := Module[{convert, ts = Flatten[{{t1, t2}, {t3, t4}}, 1][[All, 1]], hours}, convert[{h_, min_}] := h + min/60; hours = Range[Min[ts] - 1, Max[ts] + 1]; NumberLinePlot[{ convert[t1] < x < convert[t2], ...


13

Updated This happens because your DynamicModule returns a dynamic object of which x is passed on to the front-end before the scheduled task starts, so the front-end-x cannot be modified anymore by any process (more details at the end). The problem can be further simplified. This works: RemoveScheduledTask@ScheduledTasks[]; DynamicModule[{x = 0}, ...


13

Another, shorter way is Append[d, t] From the docs, DateObject[date,time] represents the specified date list and TimeObject time. If you need the list you mention in the question, just convert the DateObject using DateList: DateList@Append[d, t] (* {2012, 6, 11, 14, 1, 45.} *)


13

I worked on this problem in 2015. Here is part on my notebook from that time. A not so good algorithm. friday13th[year_Integer] := Select[DayName[#] === Friday &] @ DateRange[DateObject[{year, 1, 13}], DateObject[{year, 12, 13}], {1, "Month"}] A good algorithm. friday13th[year_Integer] := Select[DayName[#] === Friday &] @ Table[...


Only top voted, non community-wiki answers of a minimum length are eligible