Re: Module submission DateTime::Event::Predict
It's been a good long while since I've done any work on this, but I'm
gearing up to start again.
I don't think I heard any word back on whether the namespace choice
was kosher, so I guess this is the same query to the DateTime folks,
et al.
Either way I'd like to find a place that it can fit.
Thanks,
Brian
On Tue, Nov 18, 2008 at 4:17 PM, Brian Hannbrian.h...@gmail.com wrote:
Bobby,
I'm still not 100% on what method(s) I'm going to need to use. It
might end up being the case that a lot of tuning is needed to make
predictions usable. At the very least it should be able to note
regularities and flag them.
Right now this is just something that I need, and thought it would be
useful to others if it works.
Thanks,
Brian
On Tue, Nov 18, 2008 at 1:21 PM, Metz, Bobby
bobby.m...@globalcrossing.com wrote:
Brian,
How are you planning to tackle the prediction piece? Have any
particular algorithm in mind? I started speculating after reading your
e-mail, but nothing concrete jumped out at me. I thought that a purely
numerical date representation would work...using some type of standard
regression for prediction...with conversion from/to DateTime objects
simply for display. Of course that now seems impractical to me since
timezones and daylight savings irregularities would screw that up in my
mind.
B
-Original Message-
From: Brian Hann [mailto:brian.h...@gmail.com]
Sent: Monday, November 17, 2008 5:40 PM
To: Steffen Mueller
Cc: modu...@perl.org; bh...@cpan.org; datetime@perl.org
Subject: Re: Module submission DateTime::Event::Predict
I thought maybe since I would be working with DateTime objects that
would be the best fit.
If that's not the case then I'm completely open to suggestions.
Thank you,
Brian
On Mon, Nov 17, 2008 at 11:41 AM, Steffen Mueller
wyp3rl...@sneakemail.com wrote:
Hi Brian, hi DateTime people,
Perl Authors Upload Server wrote:
The following module was proposed for inclusion in the Module List:
modid: DateTime::Event::Predict
description: Predict next date from a set of dates
[...]
This module would take a set of dates (probably DateTime
objects)
and find trends in recurrence ('every Thursday', 'every weekend
day', 'every other week', 'once a month', etc) and also provide
predictions for the next date most likely to follow the set.
If workable I would think this would have any number of
applications.
[...]
I asked Dave Rolsky about this. He requested that for namespaces in
the
DateTime::* family, you should please clear your request with the
DateTime folks via their mailing list which I'm CCing.
Best regards,
Steffen, for the PAUSE admins
Re: Module submission DateTime::Event::Predict
On Mon, 8 Jun 2009, Brian Hann wrote: It's been a good long while since I've done any work on this, but I'm gearing up to start again. I don't think I heard any word back on whether the namespace choice was kosher, so I guess this is the same query to the DateTime folks, et al. The namespace seems fine to me. -dave /* http://VegGuide.org http://blog.urth.org Your guide to all that's veg House Absolute(ly Pointless) */
Re: Module submission DateTime::Event::Predict
2008/11/21 Dr.Ruud [EMAIL PROTECTED]: Flavio S. Glock schreef: =head1 CREDITS Based on an idea from Steffen Mueller [EMAIL PROTECTED] I think that should be Brian Hann: Message-ID: [EMAIL PROTECTED] Patch applied - thanks! -- Affijn, Ruud Gewoon is een tijger. Flávio S. Glock
Re: Module submission DateTime::Event::Predict
[[ This message was both posted and mailed: see the To, Cc, and Newsgroups headers for details. ]] In article [EMAIL PROTECTED], Brian Hann [EMAIL PROTECTED] wrote: I thought maybe since I would be working with DateTime objects that would be the best fit. If that's not the case then I'm completely open to suggestions. It's not that it's a bad name, but that the DateTime people are always working on DateTime and we don't necessarily keep up with what they are doing. To avoid potential problems, we just ask that people who want to put things in that namespaces send them a note to coordinate things. :) -- brian d foy (one of many PAUSE admins), http://pause.perl.org archives at http://www.xray.mpe.mpg.de/mailing-lists/modules please send all messages back to [EMAIL PROTECTED]
Re: Module submission DateTime::Event::Predict
{
package DateTime::Event::Predict;
use DateTime::Event::ICal;
use strict;
sub new {
my ($class, %params) = @_;
my $dts = DateTime::Set-from_datetimes( dates = $params{dates} );
for my $freq ( qw[ yearly monthly weekly daily hourly minutely
secondly ] ) {
my $dtr = DateTime::Event::ICal-recur( freq = $freq, dtstart
= $params{dates}[0] );
return $dtr if $dtr-contains( $dts );
}
return $dts;
}
}
# SYNOPSIS
# use DateTime::Event::Predict;
use DateTime::Format::ICal;
my $dtr = DateTime::Event::Predict-new( dates = [ DateTime-today,
DateTime-today-add( months = 1 ) ] );
print DateTime::Format::ICal-format_recurrence($dtr);
# note: format_recurrence() doesn't print 'DTSTART', but the
recurrence values are correct
=head1 CREDITS
Based on an idea from Steffen Mueller [EMAIL PROTECTED]
=head1 COPYRIGHT
Copyright (c) 2008 Flavio Soibelmann Glock.
All rights reserved. This program is free software; you can
redistribute it and/or modify it under the same terms as Perl itself.
=cut
Re: Module submission DateTime::Event::Predict
Flavio S. Glock schreef: =head1 CREDITS Based on an idea from Steffen Mueller [EMAIL PROTECTED] I think that should be Brian Hann: Message-ID: [EMAIL PROTECTED] -- Affijn, Ruud Gewoon is een tijger.
Re: Module submission DateTime::Event::Predict
Bobby,
I'm still not 100% on what method(s) I'm going to need to use. It
might end up being the case that a lot of tuning is needed to make
predictions usable. At the very least it should be able to note
regularities and flag them.
Right now this is just something that I need, and thought it would be
useful to others if it works.
Thanks,
Brian
On Tue, Nov 18, 2008 at 1:21 PM, Metz, Bobby
[EMAIL PROTECTED] wrote:
Brian,
How are you planning to tackle the prediction piece? Have any
particular algorithm in mind? I started speculating after reading your
e-mail, but nothing concrete jumped out at me. I thought that a purely
numerical date representation would work...using some type of standard
regression for prediction...with conversion from/to DateTime objects
simply for display. Of course that now seems impractical to me since
timezones and daylight savings irregularities would screw that up in my
mind.
B
-Original Message-
From: Brian Hann [mailto:[EMAIL PROTECTED]
Sent: Monday, November 17, 2008 5:40 PM
To: Steffen Mueller
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; datetime@perl.org
Subject: Re: Module submission DateTime::Event::Predict
I thought maybe since I would be working with DateTime objects that
would be the best fit.
If that's not the case then I'm completely open to suggestions.
Thank you,
Brian
On Mon, Nov 17, 2008 at 11:41 AM, Steffen Mueller
[EMAIL PROTECTED] wrote:
Hi Brian, hi DateTime people,
Perl Authors Upload Server wrote:
The following module was proposed for inclusion in the Module List:
modid: DateTime::Event::Predict
description: Predict next date from a set of dates
[...]
This module would take a set of dates (probably DateTime
objects)
and find trends in recurrence ('every Thursday', 'every weekend
day', 'every other week', 'once a month', etc) and also provide
predictions for the next date most likely to follow the set.
If workable I would think this would have any number of
applications.
[...]
I asked Dave Rolsky about this. He requested that for namespaces in
the
DateTime::* family, you should please clear your request with the
DateTime folks via their mailing list which I'm CCing.
Best regards,
Steffen, for the PAUSE admins
Re: Module submission DateTime::Event::Predict
I thought maybe since I would be working with DateTime objects that
would be the best fit.
If that's not the case then I'm completely open to suggestions.
Thank you,
Brian
On Mon, Nov 17, 2008 at 11:41 AM, Steffen Mueller
[EMAIL PROTECTED] wrote:
Hi Brian, hi DateTime people,
Perl Authors Upload Server wrote:
The following module was proposed for inclusion in the Module List:
modid: DateTime::Event::Predict
description: Predict next date from a set of dates
[...]
This module would take a set of dates (probably DateTime objects)
and find trends in recurrence ('every Thursday', 'every weekend
day', 'every other week', 'once a month', etc) and also provide
predictions for the next date most likely to follow the set.
If workable I would think this would have any number of
applications.
[...]
I asked Dave Rolsky about this. He requested that for namespaces in the
DateTime::* family, you should please clear your request with the
DateTime folks via their mailing list which I'm CCing.
Best regards,
Steffen, for the PAUSE admins
Re: Module submission DateTime::Event::Predict
Hi Brian, hi DateTime people,
Perl Authors Upload Server wrote:
The following module was proposed for inclusion in the Module List:
modid: DateTime::Event::Predict
description: Predict next date from a set of dates
[...]
This module would take a set of dates (probably DateTime objects)
and find trends in recurrence ('every Thursday', 'every weekend
day', 'every other week', 'once a month', etc) and also provide
predictions for the next date most likely to follow the set.
If workable I would think this would have any number of
applications.
[...]
I asked Dave Rolsky about this. He requested that for namespaces in the
DateTime::* family, you should please clear your request with the
DateTime folks via their mailing list which I'm CCing.
Best regards,
Steffen, for the PAUSE admins
