{"action":"created","issue":{"url":"https://api.github.com/repos/LSSTScienceCollaborations/ObservingStrategy/issues/321","repository_url":"https://api.github.com/repos/LSSTScienceCollaborations/ObservingStrategy","labels_url":"https://api.github.com/repos/LSSTScienceCollaborations/ObservingStrategy/issues/321/labels{/name}","comments_url":"https://api.github.com/repos/LSSTScienceCollaborations/ObservingStrategy/issues/321/comments","events_url":"https://api.github.com/repos/LSSTScienceCollaborations/ObservingStrategy/issues/321/events","html_url":"https://github.com/LSSTScienceCollaborations/ObservingStrategy/issues/321","id":150896181,"number":321,"title":"New material for Chapter 5.6 pending from chapter 4?","user":{"login":"willclarkson","id":13258080,"avatar_url":"https://avatars.githubusercontent.com/u/13258080?v=3","gravatar_id":"","url":"https://api.github.com/users/willclarkson","html_url":"https://github.com/willclarkson","followers_url":"https://api.github.com/users/willclarkson/followers","following_url":"https://api.github.com/users/willclarkson/following{/other_user}","gists_url":"https://api.github.com/users/willclarkson/gists{/gist_id}","starred_url":"https://api.github.com/users/willclarkson/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/willclarkson/subscriptions","organizations_url":"https://api.github.com/users/willclarkson/orgs","repos_url":"https://api.github.com/users/willclarkson/repos","events_url":"https://api.github.com/users/willclarkson/events{/privacy}","received_events_url":"https://api.github.com/users/willclarkson/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/LSSTScienceCollaborations/ObservingStrategy/labels/The%20Galaxy","name":"The Galaxy","color":"cccccc"},{"url":"https://api.github.com/repos/LSSTScienceCollaborations/ObservingStrategy/labels/Variables","name":"Variables","color":"aaaaaa"}],"state":"open","locked":false,"assignee":{"login":"lmwalkowicz","id":2147416,"avatar_url":"https://avatars.githubusercontent.com/u/2147416?v=3","gravatar_id":"","url":"https://api.github.com/users/lmwalkowicz","html_url":"https://github.com/lmwalkowicz","followers_url":"https://api.github.com/users/lmwalkowicz/followers","following_url":"https://api.github.com/users/lmwalkowicz/following{/other_user}","gists_url":"https://api.github.com/users/lmwalkowicz/gists{/gist_id}","starred_url":"https://api.github.com/users/lmwalkowicz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lmwalkowicz/subscriptions","organizations_url":"https://api.github.com/users/lmwalkowicz/orgs","repos_url":"https://api.github.com/users/lmwalkowicz/repos","events_url":"https://api.github.com/users/lmwalkowicz/events{/privacy}","received_events_url":"https://api.github.com/users/lmwalkowicz/received_events","type":"User","site_admin":false},"milestone":{"url":"https://api.github.com/repos/LSSTScienceCollaborations/ObservingStrategy/milestones/11","html_url":"https://github.com/LSSTScienceCollaborations/ObservingStrategy/milestones/Version%201%20Final%20Draft","labels_url":"https://api.github.com/repos/LSSTScienceCollaborations/ObservingStrategy/milestones/11/labels","id":1486005,"number":11,"title":"Version 1 Final Draft","description":"First version of white paper ready for internal editorial review (one month before we submit to the LSST pub board).","creator":{"login":"drphilmarshall","id":710903,"avatar_url":"https://avatars.githubusercontent.com/u/710903?v=3","gravatar_id":"","url":"https://api.github.com/users/drphilmarshall","html_url":"https://github.com/drphilmarshall","followers_url":"https://api.github.com/users/drphilmarshall/followers","following_url":"https://api.github.com/users/drphilmarshall/following{/other_user}","gists_url":"https://api.github.com/users/drphilmarshall/gists{/gist_id}","starred_url":"https://api.github.com/users/drphilmarshall/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/drphilmarshall/subscriptions","organizations_url":"https://api.github.com/users/drphilmarshall/orgs","repos_url":"https://api.github.com/users/drphilmarshall/repos","events_url":"https://api.github.com/users/drphilmarshall/events{/privacy}","received_events_url":"https://api.github.com/users/drphilmarshall/received_events","type":"User","site_admin":false},"open_issues":16,"closed_issues":65,"state":"open","created_at":"2016-01-05T22:04:23Z","updated_at":"2016-05-02T00:25:28Z","due_on":"2016-04-28T07:00:00Z","closed_at":null},"comments":38,"created_at":"2016-04-25T15:19:04Z","updated_at":"2016-05-02T20:07:41Z","closed_at":null,"body":"Hi @AshishMahabal and @lmwalkowicz -\r\n\r\n@pmmcgehee is contributing some interesting material on detecting Young Stars through Variability. Because of the way Peregrine has arranged his contribution, in the current whitepaper version this now appears as Section 4.4 (since Pull Request #391). @pmmcgehee has promised more input later today (Monday), so we are holding off on making changes (like refactoring) for a few hours. For the moment, however, you can view his material in Section 4.4 (starting on page 66 in the current version).  \r\n\r\n@akvivas and myself think this could drop very nicely into your Section 5.6 (detecting young stars through variability) that @phartigan and Christopher Johns-Krull are listed as authoring. \r\n\r\nWhen Peregrine has finished his contribution, do you have any objection to myself or @akvivas moving that material (suitably edited by us first) across to Section 5.6 and adding @pmmcgehee as an author to that section?\r\n\r\nThanks!!\r\n\r\nWill "},"comment":{"url":"https://api.github.com/repos/LSSTScienceCollaborations/ObservingStrategy/issues/comments/216347924","html_url":"https://github.com/LSSTScienceCollaborations/ObservingStrategy/issues/321#issuecomment-216347924","issue_url":"https://api.github.com/repos/LSSTScienceCollaborations/ObservingStrategy/issues/321","id":216347924,"user":{"login":"phartigan","id":18620135,"avatar_url":"https://avatars.githubusercontent.com/u/18620135?v=3","gravatar_id":"","url":"https://api.github.com/users/phartigan","html_url":"https://github.com/phartigan","followers_url":"https://api.github.com/users/phartigan/followers","following_url":"https://api.github.com/users/phartigan/following{/other_user}","gists_url":"https://api.github.com/users/phartigan/gists{/gist_id}","starred_url":"https://api.github.com/users/phartigan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/phartigan/subscriptions","organizations_url":"https://api.github.com/users/phartigan/orgs","repos_url":"https://api.github.com/users/phartigan/repos","events_url":"https://api.github.com/users/phartigan/events{/privacy}","received_events_url":"https://api.github.com/users/phartigan/received_events","type":"User","site_admin":false},"created_at":"2016-05-02T20:07:41Z","updated_at":"2016-05-02T20:07:41Z","body":"\nThanks, I'll try this. I was reforking, and as you note, it was unhappy.\n\n> Re: Updating your fork of the LSSTScienceCollaborations/ObservingStrategy\n> whitepaper\n>\n> You can do this in two ways.\n> 1 - If you do not have content in your fork which is different from the\n> main repository, and you don't care about your fork, you could delete your\n> fork (go to your fork's repository on github, go to 'Settings', then look\n> for \"Delete Repository\". You will get a big warning, but you can delete\n> your repository, which deletes your fork. Make sure you also delete any\n> cloned copies of the repository as well.)  Then hit the \"Fork\" button on\n> the original repository ( LSSTScienceCollaborations/ObservingStrategy), to\n> redo the whole fork. You will need to do a brand-new 'git clone' on your\n> local machine.\n> (simply hitting \"fork\" on the main repository doesn't work when you've\n> already forked it once .. think of it like an \"initialize the fork\" kind of\n> button).\n>\n> 2 - You can also do a PR (Pull Request) from the main repository into your\n> fork of the repository (basically, the reverse of what you did when you\n> submitted your PR to the main repo). The only tricky thing here is making\n> sure that you are requesting the PR in the \"right direction\". You should be\n> able to tell from the list of commits that the PR is asking to merge.\n> Basically:\n>   * go to https://github.com/LSSTScienceCollaborations/ObservingStrategy\n>   * click \"New PR\", then click \"Compare across forks\" on the next page\n>   * choose \"base fork\" = your fork, and \"head fork\" =\n> LSSTScienceCollaborations/ObservingStrategy   (choose \"master\" branch on\n> both)\n>   * look at the commits that will be merged into your fork (you should see\n> commits that reflect the work that's gone on since the last time you merged)\n>   * If it looks right, enter a message for the commit ('pull in updates\n> from upstream'), and click \"Create Pull Request\"\n>   * click \"merge pull request\" and then \"confirm merge\"\n> (note that you should see a message saying that there are no merge\n> conflicts .. if there are conflicts, you need to do some more work and you\n> might need some further advice, because what this means is your copy has\n> changes that never got into the LSSTScienceCollaborations/ObservingStrategy\n> fork).\n> Then go to your local-on-disk clones, and do 'git pull'.\n>\n> Lynne\n>\n> On Mon, May 2, 2016 at 10:13 AM phartigan <notifications@github.com> wrote:\n>\n>>\n>> sounds good. What's there looked like blocks of text and did not flow, but\n>> if the merge is not done then I won't worry about it. Looks like I have\n>> more to learn/setup anyway before I can incorporate changes.\n>>\n>> My sense is that FU Oris and the like will be found as a matter of\n>> course with any\n>> standard cadence. I think the main contribution will be that LSST will be\n>> able to routinely follow >10^4 TTS at least in the sky. Given that\n>> FU Oris are supposed to go off every 10^4 years or so, we ought to be able\n>> to put statistics on the frequencies of outbursts, watch them decay, etc.\n>>\n>> ph\n>>\n>> > Hey Pat,\n>> > Going over the text and editing it is actually on my plate at the\n>> moment--\n>> > I took it on at the editorial meeting and will be working on it this\n>> week.\n>> > Cheers\n>> > L\n>> >\n>> > On Mon, May 2, 2016 at 11:00 AM phartigan <notifications@github.com>\n>> wrote:\n>> >\n>> >> Hi,\n>> >>\n>> >> A couple of questions...\n>> >>\n>> >> I seem to have the ssh-keygen working. and successfully downloaded my\n>> >> github fork\n>> >> to my local machine with the clone command. However...\n>> >>\n>> >> As I feared, 'make' does not work locally because it uses a style file\n>> that\n>> >> is not in my latex package. It fails on subcaption.sty. I found\n>> >> subcaption.sty\n>> >> on the web and put it in the directory with my other .sty files, but\n>> now it\n>> >> wants a caption.sty file, because subcaption.sty depends on caption.sty.\n>> >> I'm not going to redo my latex installation for this. Is there\n>> >> a reason why the requisite style files are not bundled with the\n>> >> distribution?\n>> >>\n>> >> Also, I have a fork in my phartigan/ObservingStrategy directory on\n>> github.\n>> >> But it is before any of the text was added to the yso section. It is 266\n>> >> commits behind the LSST master. I navigated to the LSST\n>> ObservingStrategy\n>> >> directory and clicked on fork, and it looks like it did something, and\n>> >> puts me back in my phartigan directory. But the ObservingStrategy is\n>> >> not updated. I don't see how to delete my existing ObservingStrategy or\n>> >> to overwrite it.\n>> >>\n>> >> I did glance through the merged YSO section that is on the LSST site.\n>> >> The two yso contributions did not merge smoothly and I don't think\n>> >> it reads very well. I would give a try at improving it,\n>> >> but must solve these github issues first.\n>> >>\n>> >> ph\n>> >>\n>> >> [Hide Quoted Text]\n>> >> Hmm.\n>> >>\n>> >> As these are all latex documents, to see how things look presumably I'll\n>> >> run\n>> >> latex on some master file that sources the various .tex and uses some\n>> style\n>> >> file that it finds in the repository. I guess that is what `make' does?\n>> >> And the output is a .dvi or .eps or .pdf? Does my local latex version\n>> >> matter, or\n>> >> is that bundled in the repo as well, with the fonts and everything?\n>> >>\n>> >> So the purpose of the fork is that I own it and can put edits there.\n>> >> Ok, but then\n>> >> why not just edit on the fork directly, why clone? Or can't I run\n>> >> 'make' directly\n>> >> on the fork, just on a local clone? Or is it the convenience of using a\n>> >> real\n>> >> editor and unix commands and not some git-gui with green buttons on the\n>> >> web?\n>> >>\n>> >> ph\n>> >> No, you've got it Steve. The only difference is that Pat, you should\n>> clone\n>> >> using the .git address of your fork,\n>> >>\n>> >> git clone git@github.com:phartigan/ObservingStrategy.git\n>> >>\n>> >> and then push your edits there, so you can submit a pull request on the\n>> >> GitHub site. To keep up with the base repo, you'll want to connect to\n>> that\n>> >> as well, via\n>> >>\n>> >> git remote add base git@github.com:LSSTScienceColl\n>> >> aborations/ObservingStrategy.git\n>> >>\n>> >> Then you can\n>> >>\n>> >> git pull base master\n>> >>\n>> >> to bring your local repository up to date with the primary version, and\n>> >>\n>> >> git push origin master\n>> >>\n>> >> to publish your edits on your fork.\n>> >>\n>> >> On Wed, Apr 27, 2016 at 12:48 PM, StephenRidgway <\n>> notifications@github.com\n>> >> >\n>> >> wrote:\n>> >> Hi,\n>> >>\n>> >> I’m probably the least adept with GIT of any of you. I don’t know if our\n>> >> setups are similar, but when I get confused I find it clears things up\n>> to\n>> >> delete my current files and start over, as follows:\n>> >>\n>> >>\n>> >> Start in github directory.\n>> >>\n>> >> git clone git@github.com:\n>> LSSTScienceCollaborations/ObservingStrategy.git\n>> >>\n>> >> edit files in the “whitepaper” directory\n>> >>\n>> >>\n>> >> To typeset locally, use \"make\" in the whitepaper directory.\n>> >>\n>> >>\n>> >> git commit -am \"comment\"\n>> >>\n>> >>\n>> >> git status\n>> >>\n>> >>\n>> >> git push origin master\n>> >>\n>> >>\n>> >> If I’m doing anything dangerous here, hopefully somebody will point it\n>> >> out, but it seems to do what I need.\n>> >>\n>> >> Steve\n>> >> On Apr 27, 2016, at 12:35 PM, phartigan <notifications@github.com>\n>> >> wrote:\n>> >> ok. Am about done with the video. I'll probably give the figures a shot.\n>> >> I guess I make a fork, and then I edit, commit, and should see\n>> >> changes, and then\n>> >> submit a pull request. My understanding is that clones are only needed\n>> if\n>> >> I'm working locally off-line. Doesn't look like I need to create\n>> >> branches.\n>> >> Is that correct?\n>> >>\n>> >> ph\n>> >> Hi @phartigan - just to reply to your question from a few comments\n>> >> ago: I do not expect to touch youngstars.tex again today, I will be\n>> >> working on Chapter 4 issues.\n>> >>\n>> >> If you are comfortable enough with github to e.g. change figure\n>> >> boundaries or add the authors to references.bib , please go ahead\n>> >> and do so.\n>> >>\n>> >> ---\n>> >> You are receiving this because you were mentioned.\n>> >> Reply to this email directly or view it on GitHub:\n>> >>\n>> >>\n>> https://github.com/LSSTScienceCollaborations/ObservingStrategy/issues/321#issuecomment-215190543\n>> >> —\n>> >> You are receiving this because you are subscribed to this thread.\n>> >> Reply to this email directly or view it on GitHub <\n>> >>\n>> >>\n>> https://github.com/LSSTScienceCollaborations/ObservingStrategy/issues/321#issuecomment-215203790\n>> >> —\n>> >> You are receiving this because you commented.\n>> >> Reply to this email directly or view it on GitHub\n>> >> <\n>> >>\n>> https://github.com/LSSTScienceCollaborations/ObservingStrategy/issues/321#issuecomment-215207133\n>> >> >\n>> >> ---\n>> >> You are receiving this because you were mentioned.\n>> >> Reply to this email directly or view it on GitHub:\n>> >>\n>> >>\n>> https://github.com/LSSTScienceCollaborations/ObservingStrategy/issues/321#issuecomment-215225\n>> >>\n>> >> —\n>> >> You are receiving this because you were assigned.\n>> >>\n>> >>\n>> >> Reply to this email directly or view it on GitHub\n>> >> <\n>> https://github.com/LSSTScienceCollaborations/ObservingStrategy/issues/321#issuecomment-216276799\n>> >\n>> >>\n>> >\n>> >\n>> > ---\n>> > You are receiving this because you were mentioned.\n>> > Reply to this email directly or view it on GitHub:\n>> >\n>> https://github.com/LSSTScienceCollaborations/ObservingStrategy/issues/321#issuecomment-216277757\n>>\n>>\n>>\n>> —\n>> You are receiving this because you are subscribed to this thread.\n>> Reply to this email directly or view it on GitHub\n>> <https://github.com/LSSTScienceCollaborations/ObservingStrategy/issues/321#issuecomment-216297091>\n>>\n>\n>\n> ---\n> You are receiving this because you were mentioned.\n> Reply to this email directly or view it on GitHub:\n> https://github.com/LSSTScienceCollaborations/ObservingStrategy/issues/321#issuecomment-216310779\n\n\n\n"}}