[MBDyn-users] Welcome to MBDyn's GSoC!

MBDyn users list mbdyn-users at mbdyn.org
Tue May 7 15:32:05 CEST 2019

Thank you Andrea,

I appreciate it.

No problem. Before pushing any modification, I will merge request and also
communicate with you and Marco Morandini.

In this meantime, I will starting writing my first post. Also, I am going
to send a new email relating to the project soon with some questions. In
order to refine the goals and create a more detailed roadmap to achieve it.

Erivelton Gualter
Graduate Research Assistant
Control, Robotics and Mechatronics Laboratory
Cleveland State University
e.gualterdossantos at vikes.csuohio.edu

On Tue, May 7, 2019 at 9:24 AM Andrea Zanoni <andrea.zanoni at polimi.it>

> Hi Enrivelton,
> congratulations also from me! I saw your request on Gitlab, but I'm having
> trouble right now logging in to the repo (it seems like the POLIMI
> authentication system is down at the moment). As soon as I'm able to login,
> I will accept your request.
> I'll ask you to please always issue a Merge Request instead of directly
> pushing to develop, so that it is possible to discuss your modifications
> before merging them.
> Cheers
> Andrea
> On 07/05/19 15:16, Erivelton Gualter dos Santos wrote:
> On Tue, May 7, 2019 at 4:38 AM Louis Gagnon <gagnon at iag.uni-stuttgart.de>
> wrote:
>> Aditya and Erivelton:
>> Congratulations on having passed our entry tests!! As GSOC's
>> co-administrator for MBDyn I am happy to be know that you'll be working
>> with us this summer.
>> The first step is the Community Bounding. It starts now and is
>> important. It is the time you get to play with the code and get familiar
>> with each other. Consider the following:
>> * Community Bounding is not a full time commitment, but if you know
>> you'll be less available for a specific period during the summer, it can
>> be a useful buffer to get things done early
>> * if you are not yet registered to the MBDyn users mailing list, do so
>> now: http://lists.mbdyn.org/mailman/listinfo/mbdyn-users
>> * make a public post describing your project, inspire yourself from your
>> submitted proposal and use whatever public communication channel(s) your
>> want (facebook, twitter, mailing list, blog, google group, website,...)
>> as long as it can be seen by anyone without creating any account or
>> logging in to anything. Send me the link once this is done.
>> -------
>> The official **full-time** coding period begins on May 27. Consider the
>> following:
>> * treat it as a full time job with flexible working hours.
>> * we expect that you are continuously updating your mentor(s) with code
>> snippets, proposed strategies, questions, etc. This is important.
>> * During the coding period I want to receive a weekly email update from
>> each of you. It should show your progress in a clear and concise way. I
>> will periodically compile your updates into posts on the mailing list.
>> The update should be roughly 50 word long and link to related material
>> (GitHub pull requests, patch between last week's version and this week's
>> version of your code, or whatever you prefer, [please no attachments!]).
>> -------
>> During the whole program, if you have information or questions that can
>> be be of interest to the community, do not hesitate to post them to the
>> mailing list. Also, if you can answer a question on the mailing list in
>> a helpful way, please do so.
>> Keep in mind that MBDyn is a small open source project with scientific
>> applications, so you may find that it takes time to create code that
>> gets accepted by your mentors. Don't worry, this is normal.
>> Please don't expect instant replies from your mentors, especially if
>> your question requires checking your code or digging through a problem.
>> We want you to maintain parallel activities so that if you are waiting
>> for an answer from your mentor you work on another issue in the meantime
>> (documentation, helping the other GSoC student, trying a new case,
>> animating your results and posting it on youtube, making a blog post
>> explaining what you have done so far to non-experts, making a tutorial,
>> etc.).
>> Remember that there will be pass/fail evaluations every 4 weeks of
>> programming. Don't panic: if you commit to your project you should have
>> no problem getting successfully through the program.
>> -------
>> Finally, do not hesitate to email me if you have questions or concerns.
>> I check my email on workdays (generally Monday to Friday).
>> Once again, welcome to MBDyn and happy coding!!
>> -Louis
>> --
>> Louis Gagnon, Ph.D.
>> Humboldt Postdoctoral Research Fellow
>> Institut für Aerodynamik und Gasdynamik
>> Universität Stuttgart
>> Pfaffenwaldring 21, 70569, Stuttgart
>> +49 711 685 64278
>> http://louisgagnon.com/research/
>> gagnon at iag.uni-stuttgart.de
> Hello all,
> Thank you for the opportunity. I am glad I will spend the summer with you
> all.
> Also, @Louis thank you for the detailed email.
> So, relating to the *Community Bounding*, I will follow your suggestions:
>    - Get to know the code;
>    - Make a public post about the project;
>    - I have the following website [1], which I posted the Entry Test.
>       Then, I will keep posting on it;
>       - Start coding soon.
> I already have some general questions. First, I am not sure If I
> successfully registered to the Mailing list, because after I press on
> subscribe it goes to an empty page. (So, I am emailing
> mbdyn-users at mbdyn.org as well to verify if I will received it)
> Also, according to [2], I should fork the repository and checkout the
> *develop* branch; however, I am not able to fork it because I am not
> allowed. So, I requested the access on GitLab.
> [image: image.png]
> [1] - https://eriveltongualter.github.io/GSoC2019-MBDyn/entry-test.html
> [2] -
> https://public.gitlab.polimi.it/DAER/mbdyn/blob/master/CONTRIBUTING.md
> Thank you once again,
> I will keep in touch.
> Eri
> --
> Andrea Zanoni <andrea.zanoni at polimi.it> <andrea.zanoni at polimi.it>
> Dipartimento di Scienze e Tecnologie Aerospaziali
> < www.aero.polimi.it >
> Politecnico di Milano
> Ph. (+39) 02 2399 8035
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mbdyn.org/pipermail/mbdyn-users/attachments/20190507/95b7858b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 39572 bytes
Desc: not available
URL: <http://mail.mbdyn.org/pipermail/mbdyn-users/attachments/20190507/95b7858b/attachment-0001.png>

More information about the MBDyn-users mailing list