Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compile a list of lessons learned #224

Closed
SimonKrughoff opened this issue Apr 19, 2016 · 8 comments
Closed

Compile a list of lessons learned #224

SimonKrughoff opened this issue Apr 19, 2016 · 8 comments

Comments

@SimonKrughoff
Copy link
Contributor

We are learning things as we go along and I'd like to see if we can capture that. My current thinking is just to keep a running list of things here.

@drphilmarshall
Copy link
Contributor

Good idea! Something about the need for provenance, based on recent issues - @tony-johnson you had an idea for helping with that, you were going to issue it?

Also this relates to this Computing Infrastructure issue - so if we can get some ideas about the pathfinder side of things going here, maybe we can prepare to report to the CI group?

@tony-johnson
Copy link
Contributor

I have created #228 which I think is somewhat related to this issue.

@drphilmarshall
Copy link
Contributor

Cool. Passing to @SimonKrughoff to get the ball rolling. Post a lesson learned, and pass the assignment on!

@SimonKrughoff
Copy link
Contributor Author

Tag @rbiswas4. We are passing the ball around adding some lessons learned. When you have added one to the page linked in the initial message in this issue, re-assign to someone else.

drphilmarshall added a commit that referenced this issue Jul 7, 2016
@drphilmarshall
Copy link
Contributor

I just added a few lessons learned to our "Lessons Learned" page. Please start each one with a single sentence summary in bold, to aid readability! I also split the document into Runs 1 and 1.1, and Run 2, also to keep it readable. Let's all please contribute to this document today, so we can make sure to have good coverage in our talks. Click on this link and edit in your thoughts! Thanks, everyone.

cc. @DarkEnergyScienceCollaboration/twinkles

@drphilmarshall drphilmarshall changed the title Compile a lessons learned from Run1 Compile a list of lessons learned Jul 7, 2016
@rbiswas4
Copy link
Member

rbiswas4 commented Jul 8, 2016

I put in a few. Will add more if I can think of them.

@drphilmarshall
Copy link
Contributor

Thanks Rahul! @tony-johnson I put one in with your name on it! You'd better
check that I have it right. And then maybe add some more :-)

On Fri, Jul 8, 2016 at 12:27 AM, rbiswas4 notifications@github.com wrote:

I put in a few. Will add more if I can think of them.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#224 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AArY913zXZ8qiQBwU8bpNC3Krt_8p0P5ks5qTfvIgaJpZM4ILGL2
.

@drphilmarshall
Copy link
Contributor

Thanks for all your contributions to the "Lessons Learned" list - hopefully this'll be useful in formulating conclusions to our LSST DESC Notes series #284. We'll want to check back to this list when we are finishing those off, to make sure we don't miss anything. In the end, though, the record will be in the Notes, and this temporary list will be able to be retired.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment