Git Product home page Git Product logo

Comments (5)

cmrivers avatar cmrivers commented on August 28, 2024

Great catch, thanks!!
On Nov 23, 2014 8:47 AM, "jabbate" [email protected] wrote:

Just in case my message on SL data file 2014-11-10.csv gets missed, there
are inconsistencies with the data "dates" from Oct 31st onward - I am
currently going through to put the correct date for which the data are
describing, which is typically one day prior to the SitRep publication
date. On Nov 12/15th, the file names changed from reflecting the date for
the data to describing the date on which the report was published. This is
confusing. I propose changes to those file names to match the date for the
data they describe. Keeping the SitRep Version # is brilliant though. It's
a shame the health ministry does not use a date system to identify each
report in the file name!


Reply to this email directly or view it on GitHub
https://github.com/cmrivers/ebola/issues/119.[image: Web Bug from
https://github.com/notifications/beacon/ABPe9uwsLLwRLuW7W6pECuJQqOF84245ks5nQdzWgaJpZM4C_lHG.gif]

from ebola.

jabbate avatar jabbate commented on August 28, 2024

OK. Sorry for all the branching, I am trying to figure out how this shit
works!! You want me to keep going on fixing those dates? I think I've
figured out how to keep from re-branching over and over.... ?

On Sun, Nov 23, 2014 at 3:24 PM, Caitlin Rivers [email protected]
wrote:

Great catch, thanks!!
On Nov 23, 2014 8:47 AM, "jabbate" [email protected] wrote:

Just in case my message on SL data file 2014-11-10.csv gets missed,
there
are inconsistencies with the data "dates" from Oct 31st onward - I am
currently going through to put the correct date for which the data are
describing, which is typically one day prior to the SitRep publication
date. On Nov 12/15th, the file names changed from reflecting the date
for
the data to describing the date on which the report was published. This
is
confusing. I propose changes to those file names to match the date for
the
data they describe. Keeping the SitRep Version # is brilliant though.
It's
a shame the health ministry does not use a date system to identify each
report in the file name!


Reply to this email directly or view it on GitHub
https://github.com/cmrivers/ebola/issues/119.[image: Web Bug from

https://github.com/notifications/beacon/ABPe9uwsLLwRLuW7W6pECuJQqOF84245ks5nQdzWgaJpZM4C_lHG.gif]


Reply to this email directly or view it on GitHub
#119 (comment).

JL Abbate
Post-doctoral Researcher
Centre d'Ecologie Fonctionelle et Evolutive (CEFE)
CNRS - UMR 5175
1919, route de Mende
34293 Cedex 5
Montpellier, France
+1.804.212.2321 (skype/voicemail)
+33 6 95 64 21 15 (cell)
[email protected] [email protected], (preferred professional)
[email protected], (preferred personal)
[email protected]
http://people.virginia.edu/~jla8k

from ebola.

cmrivers avatar cmrivers commented on August 28, 2024

Sure if you don't mind. You can wait and submit one pull request with
multiple files if you want.
On Nov 23, 2014 9:27 AM, "jessie abbate" [email protected] wrote:

OK. Sorry for all the branching, I am trying to figure out how this shit
works!! You want me to keep going on fixing those dates? I think I've
figured out how to keep from re-branching over and over.... ?

On Sun, Nov 23, 2014 at 3:24 PM, Caitlin Rivers [email protected]

wrote:

Great catch, thanks!!
On Nov 23, 2014 8:47 AM, "jabbate" [email protected] wrote:

Just in case my message on SL data file 2014-11-10.csv gets missed,
there
are inconsistencies with the data "dates" from Oct 31st onward - I am
currently going through to put the correct date for which the data are
describing, which is typically one day prior to the SitRep publication
date. On Nov 12/15th, the file names changed from reflecting the date
for
the data to describing the date on which the report was published.
This
is
confusing. I propose changes to those file names to match the date for
the
data they describe. Keeping the SitRep Version # is brilliant though.
It's
a shame the health ministry does not use a date system to identify
each
report in the file name!


Reply to this email directly or view it on GitHub
https://github.com/cmrivers/ebola/issues/119.[image: Web Bug from

https://github.com/notifications/beacon/ABPe9uwsLLwRLuW7W6pECuJQqOF84245ks5nQdzWgaJpZM4C_lHG.gif]


Reply to this email directly or view it on GitHub
#119 (comment).

JL Abbate
Post-doctoral Researcher
Centre d'Ecologie Fonctionelle et Evolutive (CEFE)
CNRS - UMR 5175
1919, route de Mende
34293 Cedex 5
Montpellier, France
+1.804.212.2321 (skype/voicemail)
+33 6 95 64 21 15 (cell)
[email protected] [email protected], (preferred professional)
[email protected], (preferred personal)
[email protected]
http://people.virginia.edu/~jla8k


Reply to this email directly or view it on GitHub
https://github.com/cmrivers/ebola/issues/119#issuecomment-64119626.[image:
Web Bug from
https://github.com/notifications/beacon/ABPe9rZB73CdEKKEM0s6gjIxGfxvLkvuks5nQeY9gaJpZM4C_lHG.gif]

from ebola.

jabbate avatar jabbate commented on August 28, 2024

Yup! I just figured that out. I'm cranking through the Nov. dates/ data on
my one "master" fork. This is so powerful, but i'm in the "how the hell
does this work?" baby phase. Thanks for your patience! Hope I'm helping and
not slowing you down!

On Sun, Nov 23, 2014 at 3:43 PM, Caitlin Rivers [email protected]
wrote:

Sure if you don't mind. You can wait and submit one pull request with
multiple files if you want.
On Nov 23, 2014 9:27 AM, "jessie abbate" [email protected]
wrote:

OK. Sorry for all the branching, I am trying to figure out how this shit
works!! You want me to keep going on fixing those dates? I think I've
figured out how to keep from re-branching over and over.... ?

On Sun, Nov 23, 2014 at 3:24 PM, Caitlin Rivers <
[email protected]>

wrote:

Great catch, thanks!!
On Nov 23, 2014 8:47 AM, "jabbate" [email protected] wrote:

Just in case my message on SL data file 2014-11-10.csv gets missed,
there
are inconsistencies with the data "dates" from Oct 31st onward - I
am
currently going through to put the correct date for which the data
are
describing, which is typically one day prior to the SitRep
publication
date. On Nov 12/15th, the file names changed from reflecting the
date
for
the data to describing the date on which the report was published.
This
is
confusing. I propose changes to those file names to match the date
for
the
data they describe. Keeping the SitRep Version # is brilliant
though.
It's
a shame the health ministry does not use a date system to identify
each
report in the file name!


Reply to this email directly or view it on GitHub
https://github.com/cmrivers/ebola/issues/119.[image: Web Bug from

https://github.com/notifications/beacon/ABPe9uwsLLwRLuW7W6pECuJQqOF84245ks5nQdzWgaJpZM4C_lHG.gif]


Reply to this email directly or view it on GitHub
#119 (comment).

JL Abbate
Post-doctoral Researcher
Centre d'Ecologie Fonctionelle et Evolutive (CEFE)
CNRS - UMR 5175
1919, route de Mende
34293 Cedex 5
Montpellier, France
+1.804.212.2321 (skype/voicemail)
+33 6 95 64 21 15 (cell)
[email protected] [email protected], (preferred professional)
[email protected], (preferred personal)
[email protected]
http://people.virginia.edu/~jla8k


Reply to this email directly or view it on GitHub
https://github.com/cmrivers/ebola/issues/119#issuecomment-64119626.[image:

Web Bug from

https://github.com/notifications/beacon/ABPe9rZB73CdEKKEM0s6gjIxGfxvLkvuks5nQeY9gaJpZM4C_lHG.gif]


Reply to this email directly or view it on GitHub
#119 (comment).

JL Abbate
Post-doctoral Researcher
Centre d'Ecologie Fonctionelle et Evolutive (CEFE)
CNRS - UMR 5175
1919, route de Mende
34293 Cedex 5
Montpellier, France
+1.804.212.2321 (skype/voicemail)
+33 6 95 64 21 15 (cell)
[email protected] [email protected], (preferred professional)
[email protected], (preferred personal)
[email protected]
http://people.virginia.edu/~jla8k

from ebola.

cmrivers avatar cmrivers commented on August 28, 2024

No this is a huuuge help. Thanks!
On Nov 23, 2014 9:49 AM, "jessie abbate" [email protected] wrote:

Yup! I just figured that out. I'm cranking through the Nov. dates/ data on
my one "master" fork. This is so powerful, but i'm in the "how the hell
does this work?" baby phase. Thanks for your patience! Hope I'm helping
and
not slowing you down!

On Sun, Nov 23, 2014 at 3:43 PM, Caitlin Rivers [email protected]

wrote:

Sure if you don't mind. You can wait and submit one pull request with
multiple files if you want.
On Nov 23, 2014 9:27 AM, "jessie abbate" [email protected]
wrote:

OK. Sorry for all the branching, I am trying to figure out how this
shit
works!! You want me to keep going on fixing those dates? I think I've
figured out how to keep from re-branching over and over.... ?

On Sun, Nov 23, 2014 at 3:24 PM, Caitlin Rivers <
[email protected]>

wrote:

Great catch, thanks!!
On Nov 23, 2014 8:47 AM, "jabbate" [email protected]
wrote:

Just in case my message on SL data file 2014-11-10.csv gets
missed,
there
are inconsistencies with the data "dates" from Oct 31st onward - I
am
currently going through to put the correct date for which the data
are
describing, which is typically one day prior to the SitRep
publication
date. On Nov 12/15th, the file names changed from reflecting the
date
for
the data to describing the date on which the report was published.
This
is
confusing. I propose changes to those file names to match the date
for
the
data they describe. Keeping the SitRep Version # is brilliant
though.
It's
a shame the health ministry does not use a date system to identify
each
report in the file name!


Reply to this email directly or view it on GitHub
https://github.com/cmrivers/ebola/issues/119.[image: Web Bug
from

https://github.com/notifications/beacon/ABPe9uwsLLwRLuW7W6pECuJQqOF84245ks5nQdzWgaJpZM4C_lHG.gif]


Reply to this email directly or view it on GitHub
#119 (comment).

JL Abbate
Post-doctoral Researcher
Centre d'Ecologie Fonctionelle et Evolutive (CEFE)
CNRS - UMR 5175
1919, route de Mende
34293 Cedex 5
Montpellier, France
+1.804.212.2321 (skype/voicemail)
+33 6 95 64 21 15 (cell)
[email protected] [email protected], (preferred professional)
[email protected], (preferred personal)
[email protected]
http://people.virginia.edu/~jla8k


Reply to this email directly or view it on GitHub
https://github.com/cmrivers/ebola/issues/119#issuecomment-64119626.[image:

Web Bug from

https://github.com/notifications/beacon/ABPe9rZB73CdEKKEM0s6gjIxGfxvLkvuks5nQeY9gaJpZM4C_lHG.gif]


Reply to this email directly or view it on GitHub
#119 (comment).

JL Abbate
Post-doctoral Researcher
Centre d'Ecologie Fonctionelle et Evolutive (CEFE)
CNRS - UMR 5175
1919, route de Mende
34293 Cedex 5
Montpellier, France
+1.804.212.2321 (skype/voicemail)
+33 6 95 64 21 15 (cell)
[email protected] [email protected], (preferred professional)
[email protected], (preferred personal)
[email protected]
http://people.virginia.edu/~jla8k


Reply to this email directly or view it on GitHub
https://github.com/cmrivers/ebola/issues/119#issuecomment-64120282.[image:
Web Bug from
https://github.com/notifications/beacon/ABPe9hgIO4bILjXFZKnDehvrFkJFLPQ8ks5nQetmgaJpZM4C_lHG.gif]

from ebola.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.