-
Notifications
You must be signed in to change notification settings - Fork 12
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
Weekly Twinkles Task Force BlueJeans Meeting #183
Comments
I'm filling this out as if the times are Pacific. Please correct me if I'm wrong. |
You're not wrong! I clicked "enable time zone support" so you should see On Thu, Mar 17, 2016 at 9:01 AM, SimonKrughoff notifications@github.com
|
Alright, 2pm or 3pm on Tuesdays are almost unanimously popular, but we could do with hearing from @wmwv before we decide. Michael, which of those times do you prefer? Or do you want to just fill in the doodle poll at http://doodle.com/poll/ugyxusavuteav8uu and I'll pick? Thanks! |
Back from vacation last week. Poll completed. I am not available after 4pm Eastern. |
Thanks Michael! OK, everyone: 12 noon PST on Thursdays is doable by everyone at a pinch. How about we start this week, and see how we go? If you are struggling to make it at this time, we can revisit our poll. This Thursday I guess we begin the work of preparing for the Twinkles 1 data generation and processing. In other words, we'll need to spend talking about our issues. A doc for live notes is here, please feel free to jump in and help shape the agenda! |
Hi all! Looking forward to meeting up in half an hour. We'll use the usual SN group Blue Jeans room, 513427879. Our agenda is here, in our live notes file - please do take a look and add anything you'd like to talk about. And we'll want to keep notes there as we talk, so come prepared to help with that :-) Chris tells me that the Davis cosmology seminar is at 12 noon on Thursdays. @cdfassnacht, we'll talk about future meeting times with your predicament in mind! Could you fill out the doodle poll before you go to the seminar so we can see when you are free, please? Thanks! |
Good to see you all just now! Thanks for your help with the notes, and for making the new issues. I'll do some wrangling of them after lunch. Meanwhile, here's the doodle poll again, now with morning slots. Please edit your row to reflect your weekly availability! |
Is this weekly or bi-weekly (because I see that the Thursday 10am -- otherwise known as the bi-weekly Survey Simulations telecon -- slot was an option)? |
It's really weekly - I just didn't do any filtering for known conflicts. I On Thu, Mar 24, 2016 at 2:19 PM, danielsf notifications@github.com wrote:
|
Hi all! Since the doodle poll is only half-filled out, we will meet at 12 noon PDT tomorrow (Thursday March 31st) as usual. I made an agenda for us in our usual live notes file which also contains our BlueJeans room link. Comments and edits on the agenda are most welcome, as always! We need to settle on a new time for next week (when @cdfassnacht is back in CA). Could the following people please go to the doodle poll at http://doodle.com/poll/ugyxusavuteav8uu and fill in your availability before we meet? Thank you! @SimonKrughoff @jchiang87 @rbiswas4 @danielsf @sethdigel @wmwv @cdfassnacht |
Hi all, Good to talk just now. Our notes are here, for anyone who missed it. Action items are marked in red, all of these need to be issued (either afresh, or by replying to existing threads). Thanks! @cdfassnacht we punted the question of when to move this weekly meeting to until you have filled in the doodle poll - I made a start for you, just blocking out Thursday 12 noon, that you should be able to edit. Others, please do try and turn as many reds into yellows as possible to make scheduling easier. Thanks! |
Done. Sorry I have a daily class in the mornings, which eliminates the 9 Chris On Thu, Mar 31, 2016 at 1:18 PM, Phil Marshall notifications@github.com
Chris Fassnacht |
Hi all, Thanks for filling out the doodle poll. We have some options for next week, but none of them are perfect - it seems impossible to get both Chris and Michael at the same high popularity time. @cdfassnacht @wmwv are any of these three slots possible for you both? A. Weds 1pm PDT / 4pm EDT (10 yes, 0 if-needs-be, 1 no = MWV) We'll discuss this and other things at our usual weekly meeting, 12 noon PDT tomorrow, Thursday April 7th. Live notes (including agenda and BlueJeans room number) are here. Please add any items you want to talk about - if you have progress or roadblocks to report you might want to prime the notes with the links you want people to follow. Thanks, and see you tomorrow! |
The only 9, 2, 1 distribution I can see on the poll is on Tuesday ... is that a typo? |
Hi Phil, Our weekly cosmology seminars are Thursdays at noon, so I cannot make that Chris On Wed, Apr 6, 2016 at 9:45 PM, Phil Marshall notifications@github.com
Chris Fassnacht |
Right, and Michael said he could not do any late afternoons EDT. If neither A. Weds 1pm PDT / 4pm EDT (10 yes, 0 if-needs-be, 1 no = MWV) On Thu, Apr 7, 2016 at 2:23 AM, Chris Fassnacht notifications@github.com
|
Sorry to make this more complicated, but UW has a job candidate visiting, -- Scott On Thu, Apr 7, 2016 at 8:44 AM, Phil Marshall notifications@github.com
|
OK, thanks for letting us know! We'll focus on the Run 1.1 Data Release, On Thu, Apr 7, 2016 at 9:16 AM, danielsf notifications@github.com wrote:
|
Look at the time! We're meeting in 2 minutes :-) https://bluejeans.com/513427879/ |
Hi all - weekly Twinkles gathering tomorrow at 12 noon PDT, notes here as usual. Please add agenda items, so far we just have updates on NERSC setup, and Run 1.1 progress/roadblocks (ie. the registration problem). I guess we might briefly touch base on the retreat just to get things moving. What else do we need to talk about? |
I hope we are doing this today. Are we? |
Phil is on an airplane right now. I'm in a talk, but you guys should meet. |
Someone fire up PhilSim! |
@SimonKrughoff Do you want to spend this time knocking of DM-5825 ? |
Great stuffGlad this happening. Simon would you mind keeping a few notes in On Thursday, April 21, 2016, Chris Walter notifications@github.com wrote:
|
Crunching DM issues is also a good use of time of course! :-) One other thing: it'd be good to hear how the monitor is doing, esp it's On Thursday, April 21, 2016, Phil Marshall dr.phil.marshall@gmail.com
|
Happy New Year, @LSSTDESC/twinkles ! Looking fwd to catching up after the holidays in half an hour or so. Here's our agenda and live notes for the meeting, please do add agenda items as you see fit! |
Good to talk to you earlier! @heather999 the notes are ready for weeklification! Thanks :-) |
Are we going to do a doodle poll for the quarter/semester since we have a
new one?
Thanks,
Rahul
…On Thu, Jan 5, 2017 at 2:46 PM, Phil Marshall ***@***.***> wrote:
Good to talk to you earlier! @heather999 <https://github.com/heather999>
the notes are ready for weeklification! Thanks :-)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#183 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACLPjjoNhzlUTpv6QFneAtvSOIeIdYK-ks5rPXLNgaJpZM4Hyigo>
.
|
Good idea. Can you please make a poll, @rbiswas4, and post the link here?
Remember that we can only meet at times before 1pm PST. Thanks!
…On Mon, Jan 9, 2017 at 3:22 PM, rbiswas4 ***@***.***> wrote:
Are we going to do a doodle poll for the quarter/semester since we have a
new one?
Thanks,
Rahul
On Thu, Jan 5, 2017 at 2:46 PM, Phil Marshall ***@***.***>
wrote:
> Good to talk to you earlier! @heather999 <https://github.com/heather999>
> the notes are ready for weeklification! Thanks :-)
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#183 (comment)
>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/
ACLPjjoNhzlUTpv6QFneAtvSOIeIdYK-ks5rPXLNgaJpZM4Hyigo>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#183 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AArY9487DaliY-HyGGot7K9c1MQsu-64ks5rQsEigaJpZM4Hyigo>
.
|
Hi all - apologies for late notice, I alerted Slack (sort of) but didn't get this email done as well. Here's a link to the live notes for today's weekly tag-up: I'm not sure how much we have to talk about following last week's post vacation catch-up, but let's see. See you in a few mins! |
Well, after the fact, here are this week's meeting notes, ready for weeklification, @heather999 ! @SimonKrughoff @jchiang87 I noted action items for you both, that need issuing - and then we all said we'd think about a) what we want to present/discuss at the DESC Meeting Twinkles session in order to get the best out of it and b) what we want to hack/sprint on on the Friday. We'll continue that on Slack in the #twinkles channel! |
Hi all! We are meeting at our new time this week, Wednesday 0900 PST! Here's a starter agenda, in our live notes file. Mainly I guess that we should chat about the image differencing ( @SimonKrughoff @tony-johnson ) and the error model analysis ( @jbkalmbach @rbiswas4 ), but also spend some time looking at the DESC meeting schedule and chatting about possible sprints. Over breakfast, you might add any other items you want to discuss - and we'll spend more time adding items during the check in, to cope with the new early time. Looking fwd to catching up! |
@drphilmarshall I finally got back to weeklification this morning. I worked through all the previous weeklies, and will be issuing a PR from my fork later today. Thanks for not giving on me :) |
Thanks very much, @heather999 ! Today's note are now ready for weeklification too - I'll look out for the PR. Cheers! |
Hi all! Happy February :-) I made us a live notes agenda for this morning's meeting - please take a look and add notes as usual. Great if you can think about what's missing from my proposed two slides sets for the meeting, and also which parts you'll be able to prepare. Because some of the session audience will be from outside the Task Force, there'll be a certain amount of pulling together results/plots that we have already seen in our issue threads, but it'll be good to digest them further in the presence of others. I'm thinking that the slides you make will double as a plan for the Notes we will write, too - it seems hard to get them started, so its worth trying a slide-focused approach! :-) PS. @jbkalmbach @rbiswas4 I wasn't sure what to put for a science analysis discussion, great if you can add whatever you need to give us an update. @SimonKrughoff @tony-johnson a few lines of update on how the image differencing is going would be great, thanks! |
Morning @LSSTDESC/twinkles ! Let's have a short tag-up this morning, to check in on our collaboration meeting plans. With luck we can gain ourselves a good fraction of an hour to make slides in! :-) |
Alright - good luck with the slides, people! I'll update the hack day page for you. Notes are ready to weeklify, @heather999 - thanks! |
Good to catch up briefly, earlier - weekly-able notes are here, issues to follow. Thanks! |
Hi @LSSTDESC/twinkles - Looking forward to catching up at 0900 PST today! I made us a rough agenda here, please add more items and notes as usual. See you soon! |
Thanks for a good discussion earlier - the notes are now up to date, and ready for weeklification, @heather999 ! I'll work on updating the issues now. |
Morning all - let's skip the Twinkles meeting this week. It's the Project JTM in Glendale, so I think a few of us have been busy preparing for and attending that. Let's regroup next week, hopefully with some Run 1.3 products to assess! I'll ping the relevant issue thread for an interim progress report. Have good weeks! |
Morning all - let's meet up at 0900 PDT as usual to catch up on Twinkles business. I started an agenda in our live notes file here - as you can see, I think we should at least catch up on and discuss the NERSC Run 3 Level 2 processing situation, and also discuss Twinkles 2 in the light of my getting elected to Spokesperson. Anything else you want to discuss? Great if you would add a new section to teh agenda in a suitable place :-) Thanks! And see you shortly :-) |
For those of you who check email before you look at Slack, here's the notes file for this morning's Weekly Twinkles meeting. Please add anything you want to discuss in either an existing or a new section, as usual. See you soon! |
Good to see you earlier! Glad the |
Hi @LSSTDESC/twinkles - looking forward to catching up on all your progress over the last two weeks! Agenda is in our notes file, here, as usual. We have a simple 3-point agenda: progress reports on Run 3, progress reports on DESC notes, discussion of what feedback we want to give the mgmt about our DC1 experience and DC2 plans. See you soon! |
OK @heather999 the notes are ready for weeklification! Thanks :-) |
Hi @LSSTDESC/twinkles! Phil is away this week so on his behalf I've organized an agenda found in the google doc here. Take a look and let me know if we should add anything or if there's something specific I should make sure to bring up under any of the headings. Otherwise, see you tomorrow at 9am PDT. |
Hi @heather999 I think I've done the necessary work for "weeklification". Thanks! |
Thanks Bryce! :-)
…On Apr 19, 2017 12:30, "Bryce Kalmbach" ***@***.***> wrote:
Hi @heather999 <https://github.com/heather999> I think I've done the
necessary work for "weeklification". Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#183 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AArY92n62e8Vd2EUgly7itscS-pdAEluks5rxjalgaJpZM4Hyigo>
.
|
Good morning @LSSTDESC/Twinkles. Our weekly twinkles meeting is on in about 40 minutes. Notes are here. See you online soon. |
Hi @LSSTDESC/twinkles (Time Change!!) we are going to have our weekly meeting tomorrow at a different time of 1pm PDT in order to get the most updates on Run 3.1 processing. The agenda has been updated. Check it out and let me know if there's things we should add. Otherwise see you at 1:00 pm PDT tomorrow. |
Hello @LSSTDESC/twinkles ! We have a meeting tomorrow at 9 am PDT using a new conferencing system: Zoom. So make sure to go to zoom.us before the meeting tomorrow and test out your setup. Our meeting room is 571923515 and I think if you're set up you can just click here: https://zoom.us/j/571923515. Our prospective agenda is here with DESC Notes progress and Progress towards completing Twinkles 1 already there. Feel free to add anything else that you have to report. Otherwise, I'll see you tomorrow on Zoom not Blue Jeans at 9 am PDT. |
Hi @LSSTDESC/twinkles. We have our weekly meeting tomorrow morning 9 am PDT: Here’s the agenda. We’ll start off with a discussion on jupyter-dev with our guest Rollin Thomas from NERSC. |
Hi @heather999 I've filled in the remaining weekly summaries for the last few meetings and the notes are ready for weeklification |
Hi @DarkEnergyScienceCollaboration/twinkles
Hope you are enjoying the relative calm after the DESC meeting/Run 1 storm! :-) How about we meet up next week, to make a post Run 1 plan and get moving again? I think we should then meet up regularly as a Task Force: we were kind of doing that anyway, under the guise of a "reading group" #54 or to "talk about the workflow," so it should be easy to find time to get together. Having said that, it does need to be the same time slot :-)
So: please fill out this doodle poll, for a weekly Twinkles Task Force Meeting! Note that this is different from the CI and SSim working group meetings: we should be able to report to them at a moment's notice, but we have plenty to talk about just getting Twinkles going properly - so when choosing a time, we'll prioritize based on the availability of the active Twinklers (you know who you are, you little stars). Thanks! :-)
PS. I just learned that when referring to an issue like #54, if you can't remember the issue number you can just start typing eg '#readi' and GitHub autocompletes for you! Pretty nifty.
The text was updated successfully, but these errors were encountered: