profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/sarathsp06/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Sarath Sadasivan Pillai sarathsp06 @shellagilehub @messagebird @onefootball @exotel Amsterdam https://sarathsp.com/ Senior Software Engineer @shellagilehub

startedtsenart/vegeta

started time in 5 hours

startedFD-/RPiPlay

started time in 12 hours

issue commentopenjournals/joss-reviews

[PRE REVIEW]: PyGModels: A Python package for exploring Probabilistic Graphical Models with Graph Theoretical Structures

@dfm Hi ! It is really nice to here from you. The Viva-Lambda repository, is also me, a part of the code is live coded in my twitch channel (twitch.tv/vivalambda) and some of my viewers, mostly graduate students in CS, were interested in seeing the code, so I uploaded it to channel's repository as well. I can remove it, if you feel it's necessary, or add a notice to readme which repo is the original one. I tend to use the channel's repository as a scratch book (test new ideas, functionality, discover new apis, etc), and use my personal repository, D-K-E to publish more stable versions.

For the documentation, I will move the "Currently Supported Models" to doxygen main page, and continue to add doc strings to functions. Does that sound alright ?

whedon

comment created time in 15 hours

startedlunatic-solutions/lunatic

started time in 15 hours

issue commentopenjournals/joss-reviews

[PRE REVIEW]: PyGModels: A Python package for exploring Probabilistic Graphical Models with Graph Theoretical Structures

@D-K-E: Thanks for your patience! The paper is looking better, but I think that the online documentation could still use some work to make it more accessible. Right now the README seems to be the main source of documentation with the doxygen API docs hosted separately. It would be good to connect these (probably by moving most of the functionality discussion to the doxygen pages, but feel free to structure it differently) and add more context because right now it's very hard to navigate and see how the different pieces fit together.

Also, can you explain the relationship between this repo and https://github.com/Viva-Lambda/graphical-models?

whedon

comment created time in 16 hours

issue commentopenjournals/joss-reviews

[REVIEW]: kallisto: A command-line interface to simplify 2 computational modelling and the generation of atomic features.

@Sulstice I closed all issues:

  • added a python 3.7 badge
  • linked all developers in README.md
  • added @pprcht to the pyproject.toml
whedon

comment created time in 16 hours

issue commentopenjournals/joss-reviews

[REVIEW]: Riroriro: Simulating gravitational waves and calculating SNRs in Python

@wvanzeist: I've opened a tiny pull request with some minor edits to the paper. Can you take a look at that and once you've merged, please take the following steps:

  1. Comment @whedon generate pdf on this thread and read through the manuscript to make sure that you're happy with it (it's hard to make changes later!), especially author names and affiliations.
  2. Increment the version number of the software and report that version number back here.
  3. Create an archived release of that version of the software (using Zenodo or something similar). Please make sure that the metadata (title and author list) exactly match the paper. Then report the DOI of the release back to this thread.

Let me know if you have questions or run into any issues!

whedon

comment created time in 16 hours

issue commentopenjournals/joss-reviews

[REVIEW]: AltaiPony - Flare science in Kepler, K2 and TESS light curves

Thanks for your response @ekaterinailin. I think that the tight integration with Lightkurve means that not having the software compatible with Lightkurve 2 means that the software is not entirely functional. I think that it's important to be able to use the current release of Lightkurve, without pinning the installation to an old and unmaintained version of Lightkurve.

whedon

comment created time in 16 hours

issue commentopenjournals/joss-reviews

[REVIEW]: Riroriro: Simulating gravitational waves and calculating SNRs in Python

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1088/1361-6404/aaf81e is OK
- 10.1103/PhysRevD.95.024038 is OK
- 10.1093/mnras/sty908 is OK
- 10.1103/PhysRevD.85.122006 is OK
- 10.1017/pasa.2017.51 is OK
- 10.1093/mnras/sty1353 is OK
- 10.21105/joss.01987 is OK
- 10.1103/PhysRevLett.116.061102 is OK
- 10.7935/GT1W-FZ16 is OK
- 10.1103/PhysRevD.102.044055 is OK

MISSING DOIs

- None

INVALID DOIs

- None
whedon

comment created time in 17 hours

issue commentopenjournals/joss-reviews

[REVIEW]: Riroriro: Simulating gravitational waves and calculating SNRs in Python

:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:

whedon

comment created time in 17 hours

issue commentopenjournals/joss-reviews

[REVIEW]: gmr: Gaussian Mixture Regression

I submitted a new issue for my review: https://github.com/AlexanderFabisch/gmr/issues/25

whedon

comment created time in 18 hours

issue commentopenjournals/joss-reviews

[PRE REVIEW]: Precise calculations on hypercomplex numbers in C++

@melissawm will do, thanks!

whedon

comment created time in 18 hours

issue commentopenjournals/joss-reviews

[REVIEW]: TUM Open Infra Platform: an open source package for simultaneous viewing and analysis of digital models in the civil engineering domain

Just a quick line to let you know that I'm flat out working until Thursday, but I'll be able to pick up the review swiftly after that. Apologies for the delay.

whedon

comment created time in 19 hours

MemberEvent

issue commentopenjournals/joss-reviews

[PRE REVIEW]: StatSailr: Reproducible and Easy Statistics Environment with StatSailr Script

@danielskatz - I am sorry for being late. I needed to take time for my family. Testing part is now added, and it can be done with docker.

whedon

comment created time in 21 hours

fork sausheong/ish

Linux shell for iOS

https://ish.app

fork in a day

MemberEvent

issue commentopenjournals/joss-reviews

[REVIEW]: BVPy: A Python package based on FEniCS and Gmsh for solving boundary value problems in cell and tissue mechanics.

Hello @Kevin-Mattheus-Moerman. Apologies for the delay. Been occupied with a lot of teaching and admin activities. I have ticked the boxes now. Apart from my concern regarding the amount of work, everything else is fine with this library. Thank you for the opportunity once again.

whedon

comment created time in a day

issue commentopenjournals/joss-reviews

[REVIEW]: kallisto: A command-line interface to simplify 2 computational modelling and the generation of atomic features.

Ah I am catching up on the threads. @f3rmion I was reading the README first and then comments. I've begun the review and looking through the docs first. I can close some of the issues if you want me to.

For your gitbook - is there a way.I can make suggestion edits in there? or should I continue with github issues?

Apologies for taking some time to respond - weird situation over here in texas...haha

Hi @Sulstice,

no problem I totally understand the current situation. There is a separate kallisto GitBook repository. Just open issues there and I'll try to resolve them. Cheers.

whedon

comment created time in a day

MemberEvent

issue commentopenjournals/joss-reviews

[REVIEW]: GeophysicalFlows.jl: Solvers for geophysical fluid dynamics problems in periodic domains on CPUs & GPUs

@ranocha, I don't really see how I should reformat the file in view of your remark: "You should consider reformatting the license file LICENSE.md such that GitHub recognizes the license type automatically, cf. https://opensource.org/licenses/MIT"

Could you elaborate a bit perhaps?

Changing LICENSE.md from

The GeophysicalFlows.jl package is licensed under the MIT "Expat" License:

> Copyright (c) 2020: Navid C. Constantinou and Gregory L. Wagner
>
> Permission is hereby granted, free of charge, to any person obtaining a copy
> of this software and associated documentation files (the "Software"), to deal
> in the Software without restriction, including without limitation the rights
> to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
> copies of the Software, and to permit persons to whom the Software is
> furnished to do so, subject to the following conditions:
>
> The above copyright notice and this permission notice shall be included in all
> copies or substantial portions of the Software.
>
> THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
> IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
> FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
> AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
> LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
> OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
> SOFTWARE.
>

to something like

MIT License

Copyright (c) 2020: Navid C. Constantinou and Gregory L. Wagner

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

should help. You should basically use the text from the link I posted above with only minor modifications such that GitHub recognizes the license automatically and displays it in the summary part of the repo, e.g. image instead of image

whedon

comment created time in a day

issue commentopenjournals/joss-reviews

[REVIEW]: kallisto: A command-line interface to simplify 2 computational modelling and the generation of atomic features.

Ah I am catching up on the threads. @f3rmion I was reading the README first and then comments. I've begun the review and looking through the docs first. I can close some of the issues if you want me to.

For your gitbook - is there a way.I can make suggestion edits in there? or should I continue with github issues?

Apologies for taking some time to respond - weird situation over here in texas...haha

whedon

comment created time in a day

issue commentopenjournals/joss-reviews

[REVIEW]: IFermi: A python library for Fermi surface generation and analysis

Fantastic. I plan to start my review towards the latter half of next week. Looking forward to learning about IFermi!

whedon

comment created time in a day

MemberEvent

startedglassechidna/serverlessish

started time in a day