I like the R-software and everything around it. I love documentation first method to develop new tools. I share my knowledge through courses and expertise
Block or Report
Block or report statnmap
Report abuse
Contact GitHub support about this user’s behavior. Learn more about reporting abuse.
Report abusePinned
853 contributions in the last year
Less
More
Activity overview
Contributed to
inrae/diades.atlas,
ThinkR-open/fusen,
ThinkR-open/thinkrdashboard
and 39 other
repositories
Contribution activity
March 2023
Created 23 commits in 4 repositories
Created a pull request in balglave/FishMap that received 2 comments
test: Update expects for tests
tags: test Why? Need to store expected outputs as easy as possible in tests or inst/ What? Detect if we are in flat file or in test directory Up…
+29
−19
•
2
comments
Opened 8 other pull requests in 4 repositories
balglave/FishMap
4
merged
inrae/diades.atlas
1
open
1
merged
ThinkR-open/fusen
1
open
ThinkR-open/checkhelper
1
closed
Created an issue in balglave/FishMap that received 7 comments
As dev, I'd like to know the effects of same packages versions on outputs comparison
As dev, I'd like to know the effects of same packages versions on outputs comparison. We need to verify that the outputs on your machine are the sa…
8 of 17 tasks
Opened 23 other issues in 3 repositories
balglave/FishMap
2
open
17
closed
-
As dev, I'd like all unit tests around function
fm_fit_model()
to use tolerance of1e-4
-
[load_data] Update unit tests of
fm_fit_model()
to store properly the intermediate outputs -
[load_data] Update unit tests of
fm_load_data()
to store properly the intermediate outputs - As dev, I'd like to easily update my expected test outputs
-
As client, I'd like function
fm_load_data()
to be properly tested - As user, I'd like to see the difference between vignettes for developers usage, and vignettes for users
-
As user, I'd like to have all asked parameters as entry of the
fm_load_data()
correctly documented - [ci] Temporary hide windows and macos CI checks
- As dev, I'd like to know the effects of spatial resolution on outputs comparison
-
As a client, I would like the
fm_fit_model()
function to be tested on what is returned by the function - [doc] As user, I would like to have up-to-date and clear documentation
-
As user, I'd like to have more parameters available in function
fm_load_data()
- As dev, we would like Cervan to be added as contributor of the project
- [bug] As user, I'd like the spatial data preparation to work properly
- [feat] As user, I'd like to have a scheme of the use of the package
- [feat] As client, I'd like part 1 of the flat_main to be a documented and tested function
- [feat] As user, I'd like the 'main.R' file to be presented as a vignette of the package
- As dev, I'd like to know if the outputs of the model are the same between our machine and the client's machine
- [bug] As user, I'd like to be able to use the last version of spatial packages