Quantcast

[Gsoc] Reg: GSoC 2017 Project Selection

classic Classic list List threaded Threaded
4 messages Options
Siddhartha Gairola Siddhartha Gairola
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[Gsoc] Reg: GSoC 2017 Project Selection

Hello all,

I am Siddhartha Gairola (IRC nick : rocko) and wish to participate in GSoC 2017 with Scilab.

My technical skills include -
- C/C++ (advanced)
- Java (moderate)
- python (advanced)
- matlab (moderate)
- html, css, javascript
- mysql
- opengl, webgl
- opencv

Have a fair amount of experience working with git and mercurial.

I have been involved and working with scilab for the past 2 months now.
Below are the bugs and coverity fixes I have solved -

BUG FIXES (merged) -
#14012
#14812

BUG FIXES (pending to be merged) -
#6701
#13900

Coverity Issues Fixed(merged) -
#1368183, #1367380, #1098958, #1098686, #1098693, #1098655, #1098654, #1098652, #1363278, #1363279, #1371812, #1371811, #1247372, #1247359, #1191845, ##1368182, #1367384, #1367385.

Below is the link for my codereview commits -
https://codereview.scilab.org/#/q/Siddhartha

I am interested in the following projects -
1. Memory Safety - https://wiki.scilab.org/Contributor%20-%20Memory%20safety
2. Matlab MEX-Files management - https://wiki.scilab.org/Contributor%20-%20Matlab%20MEX-Files

I would be highly grateful for any inputs I could get regarding the projects and how to proceed with writing a proposal.

Thanking you.

Regards,
Siddhartha Gairola


_______________________________________________
gsoc mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/gsoc
Clément David-2 Clément David-2
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Reg: GSoC 2017 Project Selection

Hi rocko,

Thanks for this "official" introduction and all your already merged commit. About the proposal
guidelines, we strictly follow official guidelines [1]. We just have custom requirements [2], you
should :

 1. compile Scilab
 2. fix a Bug or a Coverity issue
 3. be present on the ML and/or IRC

IMHO as you have C/C++ skills, I suggest you to first focus on MEX development. Memory Safety is a
much more open subject, for experienced C++ coders or basic Java coders that can justify previous
developments.

[1]: http://write.flossmanuals.net/gsocstudentguide/writing-a-proposal/
[2]: https://wiki.scilab.org/How%20to%20apply%20to%20the%20GSOC%20%3F

--
Clément

Le dimanche 12 mars 2017 à 17:05 +0530, Siddhartha Gairola a écrit :

> Hello all,
>
> I am Siddhartha Gairola (IRC nick : rocko) and wish to participate in GSoC 2017 with Scilab.
>
> My technical skills include - 
> - C/C++ (advanced)
> - Java (moderate)
> - python (advanced)
> - matlab (moderate)
> - html, css, javascript
> - mysql
> - opengl, webgl
> - opencv
>
> Have a fair amount of experience working with git and mercurial.
>
> I have been involved and working with scilab for the past 2 months now.
> Below are the bugs and coverity fixes I have solved - 
>
> BUG FIXES (merged) - 
> #14012
> #14812
>
> BUG FIXES (pending to be merged) - 
> #6701
> #13900
>
> Coverity Issues Fixed(merged) -
> #1368183, #1367380, #1098958, #1098686, #1098693, #1098655, #1098654, #1098652, #1363278,
> #1363279, #1371812, #1371811, #1247372, #1247359, #1191845, ##1368182, #1367384, #1367385.
>
> Below is the link for my codereview commits - 
> https://codereview.scilab.org/#/q/Siddhartha
>
> I am interested in the following projects - 
> 1. Memory Safety - https://wiki.scilab.org/Contributor%20-%20Memory%20safety
> 2. Matlab MEX-Files management - https://wiki.scilab.org/Contributor%20-%20Matlab%20MEX-Files
>
> I would be highly grateful for any inputs I could get regarding the projects and how to proceed
> with writing a proposal.
>
> Thanking you.
>
> Regards,
> Siddhartha Gairola
>
> _______________________________________________
> gsoc mailing list
> [hidden email]
> http://lists.scilab.org/mailman/listinfo/gsoc
_______________________________________________
gsoc mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/gsoc
Siddhartha Gairola Siddhartha Gairola
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Reg: GSoC 2017 Project Selection

Hi Clément,
Good day!

Thank you for your reply.
I had a few questions regarding the MEX project, would be highly grateful if you could help me clarify them.

I have gone through the current mex implementation in scilab and compared it with the Matlab mex module. There are still quite a number of functions missing from the current implentation.
To be precise there are 37 functions which still have to be implemented or worked upon.
1. Does the project only require to implement the missing functions ?

I also went through the current Scilab 6 documentation and learnt how to work with it.
2. Last work had been done on the mex module as a part of a Gsoc project in 2011. Has the scilab API undergone change since then which will need to be integrated in the current mex module ?

Would be grateful for any help you could provide.

Thanking you.

Regards,
Siddhartha Gairola

On Mon, Mar 13, 2017 at 8:01 PM, Clément David <[hidden email]> wrote:
Hi rocko,

Thanks for this "official" introduction and all your already merged commit. About the proposal
guidelines, we strictly follow official guidelines [1]. We just have custom requirements [2], you
should :

 1. compile Scilab
 2. fix a Bug or a Coverity issue
 3. be present on the ML and/or IRC

IMHO as you have C/C++ skills, I suggest you to first focus on MEX development. Memory Safety is a
much more open subject, for experienced C++ coders or basic Java coders that can justify previous
developments.

[1]: http://write.flossmanuals.net/gsocstudentguide/writing-a-proposal/
[2]: https://wiki.scilab.org/How%20to%20apply%20to%20the%20GSOC%20%3F

--
Clément

Le dimanche 12 mars 2017 à 17:05 +0530, Siddhartha Gairola a écrit :
> Hello all,
>
> I am Siddhartha Gairola (IRC nick : rocko) and wish to participate in GSoC 2017 with Scilab.
>
> My technical skills include - 
> - C/C++ (advanced)
> - Java (moderate)
> - python (advanced)
> - matlab (moderate)
> - html, css, javascript
> - mysql
> - opengl, webgl
> - opencv
>
> Have a fair amount of experience working with git and mercurial.
>
> I have been involved and working with scilab for the past 2 months now.
> Below are the bugs and coverity fixes I have solved - 
>
> BUG FIXES (merged) - 
> #14012
> #14812
>
> BUG FIXES (pending to be merged) - 
> #6701
> #13900
>
> Coverity Issues Fixed(merged) -
> #1368183, #1367380, #1098958, #1098686, #1098693, #1098655, #1098654, #1098652, #1363278,
> #1363279, #1371812, #1371811, #1247372, #1247359, #1191845, ##1368182, #1367384, #1367385.
>
> Below is the link for my codereview commits - 
> https://codereview.scilab.org/#/q/Siddhartha
>
> I am interested in the following projects - 
> 1. Memory Safety - https://wiki.scilab.org/Contributor%20-%20Memory%20safety
> 2. Matlab MEX-Files management - https://wiki.scilab.org/Contributor%20-%20Matlab%20MEX-Files
>
> I would be highly grateful for any inputs I could get regarding the projects and how to proceed
> with writing a proposal.
>
> Thanking you.
>
> Regards,
> Siddhartha Gairola
>
> _______________________________________________
> gsoc mailing list
> [hidden email]
> http://lists.scilab.org/mailman/listinfo/gsoc
_______________________________________________
gsoc mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/gsoc


_______________________________________________
gsoc mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/gsoc
Clément David-3 Clément David-3
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Reg: GSoC 2017 Project Selection

Hi Siddhartha,

> To be precise there are 37 functions which still have to be implemented or worked upon.
> 1. Does the project only require to implement the missing functions ?

As I have already written, functionnal coverage is not enough. You should also document and demonstrate the use of the MEX api for existing MEX based libraries (or MEX simulink blocks).

> 2. Last work had been done on the mex module as a part of a Gsoc project in 2011. Has the scilab > API undergone change since then which will need to be integrated in the current mex module ?

AFAIK no but you might need to upgrade the current implementation to use the new api_scilab (introduced in 6.0.0) to manage struct and cell object. 

Thanks,


--

Clément



De : gsoc <[hidden email]> de la part de Siddhartha Gairola <[hidden email]>
Envoyé : dimanche 19 mars 2017 21:28:25
À : List dedicated to Scilab participation to the Google Summer of Code
Objet : Re: [Gsoc] Reg: GSoC 2017 Project Selection
 
Hi Clément,
Good day!

Thank you for your reply.
I had a few questions regarding the MEX project, would be highly grateful if you could help me clarify them.

I have gone through the current mex implementation in scilab and compared it with the Matlab mex module. There are still quite a number of functions missing from the current implentation.
To be precise there are 37 functions which still have to be implemented or worked upon.
1. Does the project only require to implement the missing functions ?

I also went through the current Scilab 6 documentation and learnt how to work with it.
2. Last work had been done on the mex module as a part of a Gsoc project in 2011. Has the scilab API undergone change since then which will need to be integrated in the current mex module ?

Would be grateful for any help you could provide.

Thanking you.

Regards,
Siddhartha Gairola

On Mon, Mar 13, 2017 at 8:01 PM, Clément David <[hidden email]> wrote:
Hi rocko,

Thanks for this "official" introduction and all your already merged commit. About the proposal
guidelines, we strictly follow official guidelines [1]. We just have custom requirements [2], you
should :

 1. compile Scilab
 2. fix a Bug or a Coverity issue
 3. be present on the ML and/or IRC

IMHO as you have C/C++ skills, I suggest you to first focus on MEX development. Memory Safety is a
much more open subject, for experienced C++ coders or basic Java coders that can justify previous
developments.

[1]: http://write.flossmanuals.net/gsocstudentguide/writing-a-proposal/
[2]: https://wiki.scilab.org/How%20to%20apply%20to%20the%20GSOC%20%3F

--
Clément

Le dimanche 12 mars 2017 à 17:05 +0530, Siddhartha Gairola a écrit :
> Hello all,
>
> I am Siddhartha Gairola (IRC nick : rocko) and wish to participate in GSoC 2017 with Scilab.
>
> My technical skills include - 
> - C/C++ (advanced)
> - Java (moderate)
> - python (advanced)
> - matlab (moderate)
> - html, css, javascript
> - mysql
> - opengl, webgl
> - opencv
>
> Have a fair amount of experience working with git and mercurial.
>
> I have been involved and working with scilab for the past 2 months now.
> Below are the bugs and coverity fixes I have solved - 
>
> BUG FIXES (merged) - 
> #14012
> #14812
>
> BUG FIXES (pending to be merged) - 
> #6701
> #13900
>
> Coverity Issues Fixed(merged) -
> #1368183, #1367380, #1098958, #1098686, #1098693, #1098655, #1098654, #1098652, #1363278,
> #1363279, #1371812, #1371811, #1247372, #1247359, #1191845, ##1368182, #1367384, #1367385.
>
> Below is the link for my codereview commits - 
> https://codereview.scilab.org/#/q/Siddhartha
>
> I am interested in the following projects - 
> 1. Memory Safety - https://wiki.scilab.org/Contributor%20-%20Memory%20safety
> 2. Matlab MEX-Files management - https://wiki.scilab.org/Contributor%20-%20Matlab%20MEX-Files
>
> I would be highly grateful for any inputs I could get regarding the projects and how to proceed
> with writing a proposal.
>
> Thanking you.
>
> Regards,
> Siddhartha Gairola
>
> _______________________________________________
> gsoc mailing list
> [hidden email]
> http://lists.scilab.org/mailman/listinfo/gsoc
_______________________________________________
gsoc mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/gsoc


_______________________________________________
gsoc mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/gsoc
Loading...