[GSoC] GSoC 2017 - Machine Learning Toolbox details - First bug help

classic Classic list List threaded Threaded
6 messages Options
BetFab BetFab
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

[GSoC] GSoC 2017 - Machine Learning Toolbox details - First bug help

Hello!
I'm Betty, I'm an engineering student in Computer Science and Applied Mathematics and I'm preparing my proposal to the Google Summer of Code with Scilab this year :).

I have read your project ideas and I have a few questions concerning the "Machine Learning" toolbox.

Indeed, it is said in the description that the algorithms can be directly implemented with the Scilab language or with already existing librairies from other languages.

I was wondering if there was a previous projects in GSOC (or other) where a library from another language was adapted in a scilab Toolbox ?  (to see how it was managed)

Indeed I am familiar with Machine Learning algorithms and could implement them with the Scilab language but I also have basic skills with Scikit-learn and Tensorflow, so wouldn't it be more interesting to use those libraries as they are already "known" by a lot of people ?

Concerning, the requirements for the application, I have successfully compiled Scilab and modified the banner (should I post the screenshot here ?).
However I need to find a first bug to fix, and need more help. I registered to Scilab bug's tracker, but from there I am kind of lost. I don't really know what to look for. Could you help me from there ?

Regards,
Betty Fabre
Caioc2 Caioc2
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [GSoC] GSoC 2017 - Machine Learning Toolbox details - First bug help

Hi,

There is no specific bugs in the ideas page for this project,
 but you can look in the ideas of development page in other projects there are various bugs
 that are not time demanding and can help you introduce yourself @ coding.
You can also code some draft or part of  a machine learning algorithm that you intend to use in this project for example.
As it can be done directly with scilab language you have plenty of choices.

On Fri, Mar 17, 2017 at 3:55 PM, BetFab <[hidden email]> wrote:
Hello!
I'm Betty, I'm an engineering student in Computer Science and Applied
Mathematics and I'm preparing my proposal to the Google Summer of Code with
Scilab this year :).

I have read your project ideas and I have a few questions concerning the
"Machine Learning" toolbox.

Indeed, it is said in the description that the algorithms can be directly
implemented with the Scilab language or with already existing librairies
from other languages.

I was wondering if there was a previous projects in GSOC (or other) where a
library from another language was adapted in a scilab Toolbox ?  (to see how
it was managed)

Indeed I am familiar with Machine Learning algorithms and could implement
them with the Scilab language but I also have basic skills with Scikit-learn
and Tensorflow, so wouldn't it be more interesting to use those libraries as
they are already "known" by a lot of people ?

Concerning, the requirements for the application, I have successfully
compiled Scilab and modified the banner (should I post the screenshot here
?).
However I need to find a first bug to fix, and need more help. I registered
to Scilab bug's tracker, but from there I am kind of lost. I don't really
know what to look for. Could you help me from there ?

Regards,
Betty Fabre



--
View this message in context: http://mailinglists.scilab.org/GSoC-GSoC-2017-Machine-Learning-Toolbox-details-First-bug-help-tp4035841.html
Sent from the Scilab / GSOC - Mailing Lists Archives mailing list archive at Nabble.com.
_______________________________________________
gsoc mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/gsoc


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

Re: [GSoC] GSoC 2017 - Machine Learning Toolbox details - First bug help

Thank you for the reply, 

- I will may be start with fixing easy potential C/C++ errors (as indicated in the 'How to contribute to Scilab' page). 

- I am currently working on the draft of a module implementing simple clustering algorithms for scilab. But as it is just a draft , I can't submit it to ATOMS, is it ok if I keep it as a Github repository for now ?

- I have read the reviews of the past Gsoc, there is several projects that aimed at using external software into Scilab, but is there an Scilab API for Python ?

regards, 
Betty Fabre 



2017-03-18 0:03 GMT+01:00 Caioc2 [via Scilab / Xcos - Mailing Lists Archives] <[hidden email]>:
Hi,

There is no specific bugs in the ideas page for this project,
 but you can look in the ideas of development page in other projects there are various bugs
 that are not time demanding and can help you introduce yourself @ coding.
You can also code some draft or part of  a machine learning algorithm that you intend to use in this project for example.
As it can be done directly with scilab language you have plenty of choices.

On Fri, Mar 17, 2017 at 3:55 PM, BetFab <[hidden email]> wrote:
Hello!
I'm Betty, I'm an engineering student in Computer Science and Applied
Mathematics and I'm preparing my proposal to the Google Summer of Code with
Scilab this year :).

I have read your project ideas and I have a few questions concerning the
"Machine Learning" toolbox.

Indeed, it is said in the description that the algorithms can be directly
implemented with the Scilab language or with already existing librairies
from other languages.

I was wondering if there was a previous projects in GSOC (or other) where a
library from another language was adapted in a scilab Toolbox ?  (to see how
it was managed)

Indeed I am familiar with Machine Learning algorithms and could implement
them with the Scilab language but I also have basic skills with Scikit-learn
and Tensorflow, so wouldn't it be more interesting to use those libraries as
they are already "known" by a lot of people ?

Concerning, the requirements for the application, I have successfully
compiled Scilab and modified the banner (should I post the screenshot here
?).
However I need to find a first bug to fix, and need more help. I registered
to Scilab bug's tracker, but from there I am kind of lost. I don't really
know what to look for. Could you help me from there ?

Regards,
Betty Fabre



--
View this message in context: http://mailinglists.scilab.org/GSoC-GSoC-2017-Machine-Learning-Toolbox-details-First-bug-help-tp4035841.html
Sent from the Scilab / GSOC - Mailing Lists Archives mailing list archive at Nabble.com.
_______________________________________________
gsoc mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/gsoc


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



If you reply to this email, your message will be added to the discussion below:
http://mailinglists.scilab.org/GSoC-GSoC-2017-Machine-Learning-Toolbox-details-First-bug-help-tp4035841p4035843.html
To unsubscribe from [GSoC] GSoC 2017 - Machine Learning Toolbox details - First bug help, click here.
NAML

paul paul
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [GSoC] GSoC 2017 - Machine Learning Toolbox details - First bug help


Hello Betty,

Good luck with the Coverity issues!

Have a look at the already pushed fixes on the codereview, not to
overlap with them.
Also, please check the headers of the files before fixing, to make sure
we have the copyright (Scilab / INRIA / Digiteo / Metalau are fine):
  https://codereview.scilab.org/#/q/status:open

You may use our forge to host your project developments:
  http://forge.scilab.org/index.php/projects

You may have a look at PIMS, but it has limitations and isn't that much
maintained:
  https://atoms.scilab.org/toolboxes/PIMS/1.1

Regards,
Paul

On 2017-03-18 13:47, BetFab wrote:

> Thank you for the reply,
>
> - I will may be start with fixing easy potential C/C++ errors (as
> indicated in the 'How to contribute to Scilab' page).
>
> - I am currently working on the draft of a module implementing simple
> clustering algorithms for scilab. But as it is just a draft , I can't
> submit it to ATOMS, is it ok if I keep it as a Github repository for
> now ?
>
> - I have read the reviews of the past Gsoc, there is several projects
> that aimed at using external software into Scilab, but is there an
> Scilab API for Python ?
>
> regards,
> Betty Fabre
>
> 2017-03-18 0:03 GMT+01:00 Caioc2 [via Scilab / Xcos - Mailing Lists
> Archives] <[hidden email] [9]>:
>
>> Hi,
>>
>> There is no specific bugs in the ideas page for this project,
>> but you can look in the ideas of development page [4] in other
>> projects there are various bugs
>> that are not time demanding and can help you introduce yourself @
>> coding.
>> You can also code some draft or part of a machine learning
>> algorithm that you intend to use in this project for example.
>> As it can be done directly with scilab language you have plenty of
>> choices.
>>
>> On Fri, Mar 17, 2017 at 3:55 PM, BetFab <[hidden email] [5]> wrote:
>>
>>> Hello!
>>> I'm Betty, I'm an engineering student in Computer Science and
>>> Applied
>>> Mathematics and I'm preparing my proposal to the Google Summer of
>>> Code with
>>> Scilab this year :).
>>>
>>> I have read your project ideas and I have a few questions
>>> concerning the
>>> "Machine Learning" toolbox.
>>>
>>> Indeed, it is said in the description that the algorithms can be
>>> directly
>>> implemented with the Scilab language or with already existing
>>> librairies
>>> from other languages.
>>>
>>> I was wondering if there was a previous projects in GSOC (or
>>> other) where a
>>> library from another language was adapted in a scilab Toolbox ?
>>> (to see how
>>> it was managed)
>>>
>>> Indeed I am familiar with Machine Learning algorithms and could
>>> implement
>>> them with the Scilab language but I also have basic skills with
>>> Scikit-learn
>>> and Tensorflow, so wouldn't it be more interesting to use those
>>> libraries as
>>> they are already "known" by a lot of people ?
>>>
>>> Concerning, the requirements for the application, I have
>>> successfully
>>> compiled Scilab and modified the banner (should I post the
>>> screenshot here
>>> ?).
>>> However I need to find a first bug to fix, and need more help. I
>>> registered
>>> to Scilab bug's tracker, but from there I am kind of lost. I
>>> don't really
>>> know what to look for. Could you help me from there ?
>>>
>>> Regards,
>>> Betty Fabre
>>>
>>> --
>>> View this message in context:
>>>
>>
> http://mailinglists.scilab.org/GSoC-GSoC-2017-Machine-Learning-Toolbox-details-First-bug-help-tp4035841.html
>>> [1]
>>> Sent from the Scilab / GSOC - Mailing Lists Archives mailing list
>>> archive at Nabble.com.
>>> _______________________________________________
>>> gsoc mailing list
>>> [hidden email] [2]
>>> http://lists.scilab.org/mailman/listinfo/gsoc [3]
>>
>> _______________________________________________
>> gsoc mailing list
>> [hidden email] [6]
>> http://lists.scilab.org/mailman/listinfo/gsoc [3]
>>
>> -------------------------
>>
>> If you reply to this email, your message will be added to the
>> discussion below:
>>
> http://mailinglists.scilab.org/GSoC-GSoC-2017-Machine-Learning-Toolbox-details-First-bug-help-tp4035841p4035843.html
>> [7]
>> To unsubscribe from [GSoC] GSoC 2017 - Machine Learning Toolbox
>> details - First bug help, click here.
>> NAML [8]
>
> -------------------------
>  View this message in context: Re: [GSoC] GSoC 2017 - Machine Learning
> Toolbox details - First bug help [10]
>  Sent from the Scilab / GSOC - Mailing Lists Archives mailing list
> archive [11] at Nabble.com.
>
>
> Links:
> ------
> [1]
> http://mailinglists.scilab.org/GSoC-GSoC-2017-Machine-Learning-Toolbox-details-First-bug-help-tp4035841.html
> [2] http:///user/SendEmail.jtp?type=node&amp;node=4035843&amp;i=1
> [3] http://lists.scilab.org/mailman/listinfo/gsoc
> [4] https://wiki.scilab.org/Ideas%20of%20development%20for%20Scilab
> [5] http:///user/SendEmail.jtp?type=node&amp;node=4035843&amp;i=0
> [6] http:///user/SendEmail.jtp?type=node&amp;node=4035843&amp;i=2
> [7]
> http://mailinglists.scilab.org/GSoC-GSoC-2017-Machine-Learning-Toolbox-details-First-bug-help-tp4035841p4035843.html
> [8]
> http://mailinglists.scilab.org/template/NamlServlet.jtp?macro=macro_viewer&amp;id=instant_html%21nabble%3Aemail.naml&amp;base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&amp;breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> [9]
> http://webmail.scilab.org/user/SendEmail.jtp?type=node&node=4035845&i=0
> [10]
> http://mailinglists.scilab.org/GSoC-GSoC-2017-Machine-Learning-Toolbox-details-First-bug-help-tp4035841p4035845.html
> [11]
> http://mailinglists.scilab.org/Scilab-GSOC-Mailing-Lists-Archives-f2646148.html
>
> _______________________________________________
> gsoc mailing list
> [hidden email]
> http://lists.scilab.org/mailman/listinfo/gsoc
_______________________________________________
gsoc mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/gsoc
BetFab BetFab
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [GSoC] GSoC 2017 - Machine Learning Toolbox details - First bug help

Hello,

I tried to solve the CID #1350547 and #1350548, so I have the patch (I attached the .diff file to this email), but how can I submit it on the codereview ?

Thank you for the help,

Regards,
Betty Fabre

2017-03-18 21:34 GMT+01:00 paul [via Scilab / Xcos - Mailing Lists Archives] <[hidden email]>:

Hello Betty,

Good luck with the Coverity issues!

Have a look at the already pushed fixes on the codereview, not to
overlap with them.
Also, please check the headers of the files before fixing, to make sure
we have the copyright (Scilab / INRIA / Digiteo / Metalau are fine):
  https://codereview.scilab.org/#/q/status:open

You may use our forge to host your project developments:
  http://forge.scilab.org/index.php/projects

You may have a look at PIMS, but it has limitations and isn't that much
maintained:
  https://atoms.scilab.org/toolboxes/PIMS/1.1

Regards,
Paul

On 2017-03-18 13:47, BetFab wrote:

> Thank you for the reply,
>
> - I will may be start with fixing easy potential C/C++ errors (as
> indicated in the 'How to contribute to Scilab' page).
>
> - I am currently working on the draft of a module implementing simple
> clustering algorithms for scilab. But as it is just a draft , I can't
> submit it to ATOMS, is it ok if I keep it as a Github repository for
> now ?
>
> - I have read the reviews of the past Gsoc, there is several projects
> that aimed at using external software into Scilab, but is there an
> Scilab API for Python ?
>
> regards,
> Betty Fabre
>
> 2017-03-18 0:03 GMT+01:00 Caioc2 [via Scilab / Xcos - Mailing Lists
> Archives] <[hidden email] [9]>:
>
>> Hi,
>>
>> There is no specific bugs in the ideas page for this project,
>> but you can look in the ideas of development page [4] in other
>> projects there are various bugs
>> that are not time demanding and can help you introduce yourself @
>> coding.
>> You can also code some draft or part of a machine learning
>> algorithm that you intend to use in this project for example.
>> As it can be done directly with scilab language you have plenty of
>> choices.
>>
>> On Fri, Mar 17, 2017 at 3:55 PM, BetFab <[hidden email] [5]> wrote:

>>
>>> Hello!
>>> I'm Betty, I'm an engineering student in Computer Science and
>>> Applied
>>> Mathematics and I'm preparing my proposal to the Google Summer of
>>> Code with
>>> Scilab this year :).
>>>
>>> I have read your project ideas and I have a few questions
>>> concerning the
>>> "Machine Learning" toolbox.
>>>
>>> Indeed, it is said in the description that the algorithms can be
>>> directly
>>> implemented with the Scilab language or with already existing
>>> librairies
>>> from other languages.
>>>
>>> I was wondering if there was a previous projects in GSOC (or
>>> other) where a
>>> library from another language was adapted in a scilab Toolbox ?
>>> (to see how
>>> it was managed)
>>>
>>> Indeed I am familiar with Machine Learning algorithms and could
>>> implement
>>> them with the Scilab language but I also have basic skills with
>>> Scikit-learn
>>> and Tensorflow, so wouldn't it be more interesting to use those
>>> libraries as
>>> they are already "known" by a lot of people ?
>>>
>>> Concerning, the requirements for the application, I have
>>> successfully
>>> compiled Scilab and modified the banner (should I post the
>>> screenshot here
>>> ?).
>>> However I need to find a first bug to fix, and need more help. I
>>> registered
>>> to Scilab bug's tracker, but from there I am kind of lost. I
>>> don't really
>>> know what to look for. Could you help me from there ?
>>>
>>> Regards,
>>> Betty Fabre
>>>
>>> --
>>> View this message in context:
>>>
>>
> http://mailinglists.scilab.org/GSoC-GSoC-2017-Machine-Learning-Toolbox-details-First-bug-help-tp4035841.html
>>> [1]
>>> Sent from the Scilab / GSOC - Mailing Lists Archives mailing list
>>> archive at Nabble.com.
>>> _______________________________________________
>>> gsoc mailing list
>>> [hidden email] [2]
>>> http://lists.scilab.org/mailman/listinfo/gsoc [3]
>>
>> _______________________________________________
>> gsoc mailing list
>> [hidden email] [6]
>> http://lists.scilab.org/mailman/listinfo/gsoc [3]
>>
>> -------------------------
>>
>> If you reply to this email, your message will be added to the
>> discussion below:
>>
> http://mailinglists.scilab.org/GSoC-GSoC-2017-Machine-Learning-Toolbox-details-First-bug-help-tp4035841p4035843.html
>> [7]
>> To unsubscribe from [GSoC] GSoC 2017 - Machine Learning Toolbox
>> details - First bug help, click here.
>> NAML [8]
>
> -------------------------
>  View this message in context: Re: [GSoC] GSoC 2017 - Machine Learning
> Toolbox details - First bug help [10]
>  Sent from the Scilab / GSOC - Mailing Lists Archives mailing list
> archive [11] at Nabble.com. > _______________________________________________
> gsoc mailing list
> [hidden email]
> http://lists.scilab.org/mailman/listinfo/gsoc
_______________________________________________
gsoc mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/gsoc



If you reply to this email, your message will be added to the discussion below:
http://mailinglists.scilab.org/GSoC-GSoC-2017-Machine-Learning-Toolbox-details-First-bug-help-tp4035841p4035861.html
To unsubscribe from [GSoC] GSoC 2017 - Machine Learning Toolbox details - First bug help, click here.
NAML


CID_1350547_1350548.diff (1K) Download Attachment
paul paul
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: [GSoC] GSoC 2017 - Machine Learning Toolbox details - First bug help


Pushing-a-commit-into-a-branch

On 03/20/2017 10:26 AM, BetFab wrote:
Hello,

I tried to solve the CID #1350547 and #1350548, so I have the patch (I attached the .diff file to this email), but how can I submit it on the codereview ?

Thank you for the help,

Regards,
Betty Fabre

2017-03-18 21:34 GMT+01:00 paul [via Scilab / Xcos - Mailing Lists Archives] <[hidden email]>:

Hello Betty,

Good luck with the Coverity issues!

Have a look at the already pushed fixes on the codereview, not to
overlap with them.
Also, please check the headers of the files before fixing, to make sure
we have the copyright (Scilab / INRIA / Digiteo / Metalau are fine):
  https://codereview.scilab.org/#/q/status:open

You may use our forge to host your project developments:
  http://forge.scilab.org/index.php/projects

You may have a look at PIMS, but it has limitations and isn't that much
maintained:
  https://atoms.scilab.org/toolboxes/PIMS/1.1

Regards,
Paul

On 2017-03-18 13:47, BetFab wrote:

> Thank you for the reply,
>
> - I will may be start with fixing easy potential C/C++ errors (as
> indicated in the 'How to contribute to Scilab' page).
>
> - I am currently working on the draft of a module implementing simple
> clustering algorithms for scilab. But as it is just a draft , I can't
> submit it to ATOMS, is it ok if I keep it as a Github repository for
> now ?
>
> - I have read the reviews of the past Gsoc, there is several projects
> that aimed at using external software into Scilab, but is there an
> Scilab API for Python ?
>
> regards,
> Betty Fabre
>
> 2017-03-18 0:03 GMT+01:00 Caioc2 [via Scilab / Xcos - Mailing Lists
> Archives] <[hidden email] [9]>:
>
>> Hi,
>>
>> There is no specific bugs in the ideas page for this project,
>> but you can look in the ideas of development page [4] in other
>> projects there are various bugs
>> that are not time demanding and can help you introduce yourself @
>> coding.
>> You can also code some draft or part of a machine learning
>> algorithm that you intend to use in this project for example.
>> As it can be done directly with scilab language you have plenty of
>> choices.
>>
>> On Fri, Mar 17, 2017 at 3:55 PM, BetFab <[hidden email] [5]> wrote:

>>
>>> Hello!
>>> I'm Betty, I'm an engineering student in Computer Science and
>>> Applied
>>> Mathematics and I'm preparing my proposal to the Google Summer of
>>> Code with
>>> Scilab this year :).
>>>
>>> I have read your project ideas and I have a few questions
>>> concerning the
>>> "Machine Learning" toolbox.
>>>
>>> Indeed, it is said in the description that the algorithms can be
>>> directly
>>> implemented with the Scilab language or with already existing
>>> librairies
>>> from other languages.
>>>
>>> I was wondering if there was a previous projects in GSOC (or
>>> other) where a
>>> library from another language was adapted in a scilab Toolbox ?
>>> (to see how
>>> it was managed)
>>>
>>> Indeed I am familiar with Machine Learning algorithms and could
>>> implement
>>> them with the Scilab language but I also have basic skills with
>>> Scikit-learn
>>> and Tensorflow, so wouldn't it be more interesting to use those
>>> libraries as
>>> they are already "known" by a lot of people ?
>>>
>>> Concerning, the requirements for the application, I have
>>> successfully
>>> compiled Scilab and modified the banner (should I post the
>>> screenshot here
>>> ?).
>>> However I need to find a first bug to fix, and need more help. I
>>> registered
>>> to Scilab bug's tracker, but from there I am kind of lost. I
>>> don't really
>>> know what to look for. Could you help me from there ?
>>>
>>> Regards,
>>> Betty Fabre
>>>
>>> --
>>> View this message in context:
>>>
>>
> http://mailinglists.scilab.org/GSoC-GSoC-2017-Machine-Learning-Toolbox-details-First-bug-help-tp4035841.html
>>> [1]
>>> Sent from the Scilab / GSOC - Mailing Lists Archives mailing list
>>> archive at Nabble.com.
>>> _______________________________________________
>>> gsoc mailing list
>>> [hidden email] [2]
>>> http://lists.scilab.org/mailman/listinfo/gsoc [3]
>>
>> _______________________________________________
>> gsoc mailing list
>> [hidden email] [6]
>> http://lists.scilab.org/mailman/listinfo/gsoc [3]
>>
>> -------------------------
>>
>> If you reply to this email, your message will be added to the
>> discussion below:
>>
> http://mailinglists.scilab.org/GSoC-GSoC-2017-Machine-Learning-Toolbox-details-First-bug-help-tp4035841p4035843.html
>> [7]
>> To unsubscribe from [GSoC] GSoC 2017 - Machine Learning Toolbox
>> details - First bug help, click here.
>> NAML [8]
>
> -------------------------
>  View this message in context: Re: [GSoC] GSoC 2017 - Machine Learning
> Toolbox details - First bug help [10]
>  Sent from the Scilab / GSOC - Mailing Lists Archives mailing list
> archive [11] at Nabble.com. > _______________________________________________
> gsoc mailing list
> [hidden email]
> http://lists.scilab.org/mailman/listinfo/gsoc
_______________________________________________
gsoc mailing list
[hidden email]
http://lists.scilab.org/mailman/listinfo/gsoc



If you reply to this email, your message will be added to the discussion below:
http://mailinglists.scilab.org/GSoC-GSoC-2017-Machine-Learning-Toolbox-details-First-bug-help-tp4035841p4035861.html
To unsubscribe from [GSoC] GSoC 2017 - Machine Learning Toolbox details - First bug help, click here.
NAML


CID_1350547_1350548.diff (1K) Download Attachment


View this message in context: Re: [GSoC] GSoC 2017 - Machine Learning Toolbox details - First bug help
Sent from the Scilab / GSOC - Mailing Lists Archives mailing list archive at Nabble.com.


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

-- 
Paul BIGNIER
Development engineer
-----------------------------------------------------------
Scilab Enterprises
143bis rue Yves Le Coz - 78000 Versailles, France
Phone: +33.1.80.77.04.68
http://www.scilab-enterprises.com

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