Document changes

[ErvanCH]

Hi Mauro,

Thanks for your help. I am working in background to fix/update/examplify the functions. While running my code again for my paper, I got a strange behaviour and I found the problem.
In function "computeAGB" (l, 466-481), you probably cleaned up the following expression

df['Family' == "Arecaceae", "agb" := agbPalm(dbh2)]
by
df["Family" == "Arecaceae", "agb" := agbPalm(dbh2)]

However, data.table doesn't know how to deal with " " and fails to do the job (and messed up my whole analysis).
Shall I kindly ask you to document all changes that you are doing for me to double check, please.
Thanks
Ervan

[maurolepore]

Hi Ervan,

• I'm very sorry for that. I'm surprised that styler doesn't account for that issue. Maybe we should report it as a bug?

• But how could I get an output then? Can you send me the code that exposed this problem?

---

• All changes are documented -- mine and yours. Git takes care of that automatically. To review what I did you need to inspect my commits. Also, I make my best to link each commit message to a relevant issue. For example, notice how my commit is linked to issue 16:

• If you click on the commit message, you'll jump to the actual files that changed and you can inspect them in Split mode. For example, here is the relevant line:

[ErvanCH]

Sure. No worries. It also arises from my incompetence in proofreading and checking version. I haven't really look for detailed information, but it might be good if you want to make a short tuto and the very basic of collaborative work through Git. For instance, showing how to check changes in version, restore or accept corrections. Similarly, have the key steps of developing a R package from scratch would be very useful. From my experience, I got a bit lost and don't know where to start... Currently, I am working locally to make sure that everything works properly. Does it mean that we'll need to go through all the steps you did in checking the data? Thanks Ervan

…

On Tue, Oct 23, 2018 at 1:49 PM Mauro Lepore ***@***.***> wrote: Hi Ervan, - I'm very sorry for that. I'm surprised that *styler* doesn't account for that issue. Maybe we should report it as a bug? [image: image] <https://user-images.githubusercontent.com/5856545/47358071-ae268a80-d696-11e8-81f6-60219c05990f.png> - But how could I get an output then? Can you send me the code that exposed this problem? ------------------------------ - All changes are documented -- mine and yours. Git takes care of that automatically. To review what I did you need to inspect my commits <https://github.com/forestgeo/AGBfluxes/commits/master>. Also, I make my best to link each commit message to a relevant issue. For example, notice how my commit is linked to issue 16 <#16>: [image: image] <https://user-images.githubusercontent.com/5856545/47358257-415fc000-d697-11e8-96ba-1ca45d99f327.png> - If you click on the commit message, you'll jump to the actual files that changed and you can inspect them in *Split* mode. For example, here is the relevant line <608e8a8#diff-ad7728904db442dd2086f701c27dd40cR285> : [image: image] <https://user-images.githubusercontent.com/5856545/47357925-35bfc980-d696-11e8-98ec-98b206c55992.png> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#29 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATScdby8pachboVJCMR1iJtcavK5bmbUks5unwJcgaJpZM4X0wcy> .

--

_____________________________ Ervan Rutishauser, PhD ​ <http://carboforexpert.ch/>STRI post-doctoral fellow ​Skype: ervan-CH

[maurolepore]

Git and GitHub

Be kind to yourself and patient. GitHub has great tools for collaboration but it takes a lot of practice to become fluent. You are doing stuff that I think is of advanced level.

I haven't really look for detailed information ...
There is too much information out there. Whenever I get stuck I generally start here: https://help.github.com/.

It might be good if you want to make a short tuto and the very basic of collaborative work through
Git. ... how to:

• check changes in version,
• restore or accept corrections.

Sure. I applaud your determination to learn this stuff. We can organize a video-chat, but first I suggest you read these two short resources:

2. https://guides.github.com/introduction/flow/

Once you are fluent with reviewing pull requests, I can stop working on master branch and instead work on branches dedicated to pull requests. You could even remove my privilege to push into master. Then it'll be up to you to review and merge my pull requests into master. At the beginning this workflow may slow you down. But in the long run it is certainly the way to go.

Packages

Similarly, have the key steps of developing a R package
from scratch would be very useful. From my experience, I got a bit lost and
don't know where to start...

Sure, both of

[maurolepore]

Be kind to yourself. We are doing advanced stuff.

Can you video-chat this week? First please read this two short documents:

1. https://help.github.com/articles/about-pull-requests/
2. https://guides.github.com/introduction/flow/

RE: Packages, sure. I'm always happy to talk about building packages. We'll likely need to do this in another meeting. Otherwise it'll be too much stuff to digest.

What I use every time I build a new package is this checklist.

For some background, I remind you of these two resources:

• Video tutorials (short; only (1) Packages and R Code; (2) Documentation and maybe (3) Unit testing).
• R packages (this is the best resource and you should read it whenever you can).

Also I recently discovered the rOpenSci's packaging guide (medium).

[maurolepore]

@ervanSTRI,

RE

... data.table doesn't know how to deal with " ".

Can you create a minimal example that reproduces the problem? The only issue related to data.table that might have some connection is this r-lib/styler#445 (and it has been fixed).