Re: [Stellarium-pubdevel] ESA SOCIS 2015 - Irregular Solar System bodies

[Alejandro G. M. <ale...@gm...>]

Dear Mr Zotti,

Thank you for your answer and for all the tips about the implementation :)

But I don't know if I understood the "1 seat only" issue. I thought you
could have one student for each project, not just one for the whole
organization!

Hence, I thought this Irregular Solar System bodies project was covered by
someone else in the programme. But after your email I understand this
project is not assigned to anyone, isn't it?
If this is the case, I wil have it into account for when I finish my final
exams. Let's see what happens, if I have some time I would love to
collaborate in a free software project like this one.

Thank you very very much for your attention, and good luck also to you with
SOCIS! :)

Best regards,
Alejandro

P.D.: I also wanted to thank you for your work (and all the developers
work) in Stellarium. It was of great help when we were working in GranaSAT;
we used it before the flight to have an idea of the light conditions and
the visible stars we would have that night, up there in the stratosphere,
and to test the camera with which we photographed the sky, as well as our
star tracker algorithm. Thank you all! :)

2015-04-27 12:39 GMT+02:00 Georg Zotti <geo...@un...>:

> Dear Alejandro!
>
> Also from me, thank you for your interest, and I also regret we cannot
> offer more than one seat. If you are willing to implement the OBJ
> adaptations for irregular planetary bodies without funding, you are of
> course more than very welcome to do so - we are always in neeed for good
> people! Just create your own branch in Launchpad and start coding. We can
> of course offer some guidance.
>
> In principle it should be possible to move the OBJ loader to the main
> program core and adapt it accordingly to be used both in Scenery3D and for
> the 3D models used in the Planet class (and subclasses). It would require
> adding an optional 3D model to be imported at planet loading time and
> changing the method Planet::draw3dModel() accordingly. The struct
> Planet3DModel can be easily filled from the OBJ file format. Just be
> certain about proper axis orientation (if even known for the bodies), you
> know Y/Z is sometimes swapped in OBJ.
>
> Kind regards, and good luck finding another SOCIS project (and/or with OBJ
> planets for Stellarium :-)
>
> Georg Zotti
>
>
> On Mo, 27.04.2015, 08:14, Alejandro Garcia Montoro wrote:
> > Dear Mr Wolf,
> >
> > Thank you very much for such a quick response and for your feedback :)
> >
> > Maybe, after all the time I put in this, I do not wait until next year
> but
> > try to collaborate with Stellarium in the following months :) I will be
> > attentive to the mailing list and the bug tracker and see if I can be of
> > any help.
> >
> > And I will also try with other SOCIS projects, do not worry! Thank you
> > again for the quick response :)
> >
> > Best regards,
> > Alejandro
> > El 27/04/2015 06:30, "Alexander Wolf" <ale...@gm...> escribió:
> >
> >> Dear Alejandro,
> >>
> >> thank you for your interest in Stellarium and application to SOCIS'15.
> >>
> >> 2015-04-27 6:37 GMT+06:00 Alejandro Garcia Montoro <
> >> ale...@gm...>:
> >>
> >>> I have downloaded some of the 3D models I have found in the NASA
> >>> website
> >>> and I am trying to render them in Stellarium. My first idea was to
> >>> reuse
> >>> the OBJ loader code of the Scenery3d plugin, but I still have to study
> >>> the
> >>> pros and cons of this solution.
> >>>
> >>
> >> It's good idea, because OBJ reader can be implemented as part of the
> >> core.
> >>
> >>
> >>> Regarding this issue, I have some doubts about the asteroid rendering
> >>> process and the idea you have: I understand all the asteroid processing
> >>> has
> >>> to be done in the MinorPlanet module, isn't it?
> >>>
> >>
> >> Yes, it is correct.
> >>
> >>
> >>> Is the idea to update this class in order to render the 3D models (in
> >>> the
> >>> case they are available), or the work has to be done in the draw3dModel
> >>> method of the parent module? Or you just want to add it as a new module
> >>> or
> >>> plugin?
> >>>
> >>
> >> Well, it's good question. If we'll limited using of the models for minor
> >> planets only then we should extend MinorPlanet class. If you want using
> >> models for comets, planets and moons (generic case), then we should
> >> implement support of models in Planet class (main class for rendering of
> >> the Solar system bodies). Personally for me good case will be
> >> implementation to the generic case for rendering of models - we can use
> >> models for irregular moons, like Phobos.
> >>
> >>
> >>>
> >>> Finally, I also wanted to know what do you want the students exactly to
> >>> write in the application. I am sketching a timing schedule that I will
> >>> include, along with the first ideas I have for the implementation of
> >>> the
> >>> project and my technical background. If you need anything else, please,
> >>> let
> >>> me know.
> >>>
>
>
>