AGU Abstract - Highlighting contributions

[SimonGoring]

Hi all, we intend to submit an abstract that highlights some of the work done at the C4P Development Workshop. With that in mind I wanted to check in to see what progress (if any) you had made over the past month, and whether there are plans to develop this further in the next two months.

Ideally we would provide two slides for each working group to highlight the scientific achievements from this hackthon. I can support some work over the next two months if you can provide me with specific tasks through the Issues tracker. Please let me know.

[CommonClimate]

@SimonGoring I have not done any more work on this since the workshop, best ask Scott Farley and other members .

[nickmckay]

I have done a bit refining the neotoma2lipd function..., which is a simple (but important I think tool), not a major scientific achievement yet

[SimonGoring]

Thanks both. Any chance you could create an issue that summarizes what needs to be completed for this repo to be "done"?

@nickmckay do you want to put the neotoma2lipd function into the neotoma R package? Or will it go into a lipd R package? I just looked at it and it looks like it should be relatively simple to generalize into something that works on site, dataset and download objects. If you want, push the newest changes & tag me. Where does it go once it's in the lipd format? Is there a way to upload to the wiki directly?

[nickmckay]

Re: the repo being "done" - it's a bit of random collection of things at this point, with the wiki data pulling being more of test case than something that can be broadly applied I think. I guess I'm not certain that the repo has a long term future, and should be assimilated elsewhere.

@SimonGoring re: neotoma2lipd, it probably makes sense for now to have it as part of the lipdR package, until/unless there's something that neotoma or it's users want to do with data in lipd form. There's not a way to upload in R to the wiki yet, but can upload via the web and a lipd file.

[SimonGoring]

Thanks @nickmckay. Is the lipdR package up, or going to go up somewhere? If it is, then I can add the extra methods to the function. Or is it just part of the geochronR package?

If possible, could one of you (either you or @CommonClimate) edit the README to reflect the current status of the repo?

[nickmckay]

lipdR and geochronR packages are both under heavy development and will be available shortly.... I'll point you there when it's up. Thanks @SimonGoring . @CommonClimate can you update the readme? If not I can probably figure out how to do that.

[aklima]

Sorry for delay in responding, was out in the field, going back out tomorrow.

Nothing specifically for ClimateLife. Have been working off and on to hook the XML output from Neotoma into the javascript graphing website I was working on. Nothing ready to show

-Anna

On Tue, Aug 2, 2016 at 1:08 PM, Simon notifications@github.com wrote:

Assigned #1 https://github.com/cyber4paleo/ClimateLife/issues/1 to @aklima https://github.com/aklima.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cyber4paleo/ClimateLife/issues/1#event-742938308, or mute the thread https://github.com/notifications/unsubscribe-auth/AIHKEeAvstfsg4D4fKP7DLw2gyhGxRZLks5qb6OwgaJpZM4Ja_18 .

[SimonGoring]

Thanks @aklima, hope the field work goes well!