Whisker plots about stile HOT 12 CLOSED

this sounds like something easy (?) I could volunteer for, as a means of forcing myself to learn how to work with the code. Unless someone already has this part? Hironao sent around some whisker plots to the HSC lists. Was that already with Stile? Should I start with what Hironao already has, or start from scratch? Since Steve is here at IPMU, I could also volunteer to work with Steve to get some whisker plots running on Master and try to work to get those interfaced with an interface like PipeQA. Is this a good suggestion, or are those too big steps to start with?

from stile.

It is not with stile. I am happy to share my code. However, I agree that we may want to wait until we make a decision on #3 .

from stile.

I'd be very happy to have you work on this, sure!

I'm actually on the fence about waiting on the decisions in #3, although I know I'm the one who brought it up. Since this is the first thing that is heavy on the presentation side, maybe we should let you/whoever works on this decide the best way to structure the making-plots part of the code. (And then we can all chime in when you do a pull request, of course...)

One detail: we can plot things using displayQA but we should stay away from the full (and separate) PipeQA framework, since that requires the HSC/LSST stack as a prerequisite. I wasn't sure if your mention was a question of terminology or not, so that may have been what you were thinking anyway--just wanted to be clear!

I'm going to have a go at writing the interface to the butler over the next ~week or two. Are you all right starting to work with the dummy data handler & data set in the test/ directory for now?

from stile.

Yes, I should be ok with the dummy data for now. And yes, I meant to say "displayQA", not "pipeQA".

On May 27, 2014, at 11:47 AM, msimet wrote:

I'd be very happy to have you work on this, sure!

I'm actually on the fence about waiting on the decisions in #3, although I know I'm the one who brought it up. Since this is the first thing that is heavy on the presentation side, maybe we should let you/whoever works on this decide the best way to structure the making-plots part of the code. (And then we can all chime in when you do a pull request, of course...)

One detail: we can plot things using displayQA but we should stay away from the full (and separate) PipeQA framework, since that requires the HSC/LSST stack as a prerequisite. I wasn't sure if your mention was a question of terminology or not, so that may have been what you were thinking anyway--just wanted to be clear!

I'm going to have a go at writing the interface to the butler over the next ~week or two. Are you all right starting to work with the dummy data handler & data set in the test/ directory for now?

—
Reply to this email directly or view it on GitHub.

from stile.

@alexieleauthaud , my code is not so fancy that it might need rewriting, but I think it will give a good starting point. Do you want me to send you a code with an example?

from stile.

Hi Alexie--I just merged some code into the master branch, so if you've already started work on this, you'll also need to follow the directions I just gave Song in #4 (with a different branch name, obviously). Let me know if you have any trouble!

from stile.

Got it, thanks! Yes, I'm terribly slow on this, sorry. It is a bit of a learning curve getting going, I haven't started yet but I'm keen to get started this week if I can find time.

On Jun 8, 2014, at 5:45 AM, msimet wrote:

Hi Alexie--I just merged some code into the master branch, so if you've already started work on this, you'll also need to follow the directions I just gave Song in #4 (with a different branch name, obviously). Let me know if you have any trouble!

—
Reply to this email directly or view it on GitHub.

from stile.

Alexie - if you need help figuring out things like making a branch to work on, or any other aspect of git workflow, you can post your questions on here. :)

Let me also mention something that was useful to me when I started using git:
Since it’s not a centralized repository but rather a distributed version control system, this means that if you screw stuff up locally when you make commits (mess up a merge between your changes and someone else or whatever), you haven’t messed up anyone else as long as you don’t push those commits. Once you push them it gets more complicated to fix problems - we had a case in the private great3 repository when Jim Bosch basically had to do some complicated fix to a branch and nobody could touch it until he was done. But if you make some mistakes when merging stuff and you think the branch is messed up, then you can just blow away your version of the repository, re-clone it, and you’ll be back to the latest version of the repository before the mess happened.

Not to assume that you’ll make a mess, but, well, I did a few times on GalSim and it was really reassuring once I realized that I hadn’t messed up everybody with my mistakes as long as they weren’t pushed.

from stile.

Alexie, I have some basic python codes for whisker which were used for generating plots I posted to the mailing list. If you want, I will send them to you.

from stile.

Sure, that would be great Hironao. It me give me a good example to get started, thanks!
And thank you Rachel for the tips on merging with git, very helpful. I don't have any particular questions right now, just need to find time to get started!

On Jun 9, 2014, at 9:59 AM, Hironao Miyatake wrote:

Alexie, I have some basic python codes for whisker which were used for generating plots I posted to the mailing list. If you want, I will send them to you.

—
Reply to this email directly or view it on GitHub.

from stile.

(I sent the example to Alexie offline.)

from stile.

@alexieleauthaud - I just noticed we don't seem to have a comparable file here in Stile, so you might want to check out this file about workflow with git in the GalSim repo,
https://github.com/GalSim-developers/GalSim/blob/master/devel/git.txt

We were going to adopt basically the same workflow in terms of branch structure and so on.

from stile.