Systems documentation, adding a new system and vehicle

[Onur Guzel]

Hello

1.Is there a naming convention while giving names to the systems, like lctr-b2xx, ntnu-b2xx? What does b2xx and other suffixes stand for?

2.Is there a documentation for adding a new system configuration for Dune and Glued? I searched in the Internet but I did not find a step by step guide. Is it ok to write and publish one for this, I mean may I write one, (sure after I understand whole steps).
Where can I find a documentation about adding a new system and adding a new vehicle to glued and dune?

3.I am trying to add a new sea vehicle, not an underwater sea vehicle but I plan to build three different vehicles. Is it ok to add them like under glued system folder.

glued/
systems/
mysystem-code(b2xx, a6xx sth.)/
vehicle1. cfg
vehicle2. cfg
vehicle3. cfg

4.Is there a documentation about adding a new vehicle and the dune task configuration for it? I mean the dune ini files. I am just checking the dune and glued source code and samples, then trying to add configurations for the new vehicle. If there is no documentation about those things, writing one can be useful. I will be glad to write one.

5. How can I help the project?

6. Where can I see the glued and dune issues
and start helping to the project? Can I contribute my code?

Thanks

Regards

[José Pinto]

Hi Onur,

On Sun, Jan 22, 2017 at 10:23 PM, Onur Guzel <onur....@gmail.com> wrote:

Hello

1.Is there a naming convention while giving names to the systems, like lctr-b2xx, ntnu-b2xx? What does b2xx and other suffixes stand for?

Those names are the names of the hardware devices they provide support for. You can create new ones as needed, for instance onur-asv.

 

2.Is there a documentation for adding a new system configuration for Dune and Glued? I searched in the Internet but I did not find a step by step guide. Is it ok to write and publish one for this, I mean may I write one, (sure after I understand whole steps).
Where can I find a documentation about adding a new system and adding a new vehicle to glued and dune?

I'm afraid you'll have a bad time finding it as this distribution is maintained only by 2-3 people. I suggest adapt (packages, kernel configuration) an existing system to yours.

 

3.I am trying to add a new sea vehicle, not an underwater sea vehicle but I plan to build three different vehicles. Is it ok to add them like under glued system folder.

glued/
     systems/
            mysystem-code(b2xx, a6xx sth.)/
                 vehicle1. cfg
                 vehicle2. cfg
                 vehicle3. cfg

Yes this would be the best direction.

 

4.Is there a documentation about adding a new vehicle and the dune task configuration for it? I mean the dune ini files. I am just checking the dune and glued source code and samples, then trying to add configurations for the new vehicle. If there is no documentation about those things, writing one can be useful. I will be glad to write one.

Again, the best is to adapt existing configurations to your needs. Just for curiosity, what kind of hardware (CPU, sensors) will you be using?

 

5. How can I help the project?

If you can contribute the documentation this would greatly benefit the project. We can revise prior to posting it on the project's wiki.

 

6. Where can I see the glued and dune issues
and start helping to the project? Can I contribute my code?

I suggest you create a for and edit the wiki on that fork. We can later merge your changes and give you credit on the main project.

Regards,

José

[José Braga]

Hi Onur,

Although I am no longer affiliated with University of Porto, here are my two cents about this:

2017-01-22 22:23 GMT+00:00 Onur Guzel <onur....@gmail.com>:

Hello

1.Is there a naming convention while giving names to the systems, like lctr-b2xx, ntnu-b2xx? What does b2xx and other suffixes stand for?

I believe LCTR stands for Lsts ConTRoller. The rest I am not sure (it was like that before I started working there), 

 guess it was a naming scheme applied to all things over there. 

Right now ntnu is the folder where NTNU guys stored their configurations.

LCTR-B2XX is for beaglebone armv7 computers.

 

2.Is there a documentation for adding a new system configuration for Dune and Glued? I searched in the Internet but I did not find a step by step guide. Is it ok to write and publish one for this, I mean may I write one, (sure after I understand whole steps).
Where can I find a documentation about adding a new system and adding a new vehicle to glued and dune?

There isn't. You surely can. So far, the available configurations on DUNE/GLUED for LSTS systems

were created by people who managed the whole software, so documentation is scarce

 

3.I am trying to add a new sea vehicle, not an underwater sea vehicle but I plan to build three different vehicles. Is it ok to add them like under glued system folder.

glued/
     systems/
            mysystem-code(b2xx, a6xx sth.)/
                 vehicle1. cfg
                 vehicle2. cfg
                 vehicle3. cfg

folders like lctr-a6xx, lctr-a8xx are built for systems with different architectures.

geode x86 for lctr-a6xx, atom x86 for lctr-a8xx, igep armv7 for lctr-a9xx...

if your systems share the same CPU architecture, that's alright.

my suggestion is to have a folder with your company/initials first (e.g: onur-systems)

4.Is there a documentation about adding a new vehicle and the dune task configuration for it? I mean the dune ini files. I am just checking the dune and glued source code and samples, then trying to add configurations for the new vehicle. If there is no documentation about those things, writing one can be useful. I will be glad to write one.

thanks. all documentation available is on github' wikis, which is very small, so any help would be welcomed

 

5. How can I help the project?

usually, the access to the main repos is for the University of Porto, and very seldomly they open the access to people from outside.

But, using git fork systems, you can fork the projects and then, if you believe you can add to the project launch Pull Request to ask

something to be merged.

On the other hand, if you have suggestions for new features and functionalities, you can ask/suggest them. and if the powers that be

agree with you and man-power is available, they can add it to the code :)

 

6. Where can I see the glued and dune issues
and start helping to the project? Can I contribute my code?

you can contribute your code, by forking the repos.

regarding, glued/dune issues, right now University of Porto has none opened in their internal tracking system.

I guess they can start adding bugs/issues on the public tracker henceforth. This does not mean everything is ok, it surely isn't,

and there are a lot of functionalities they wish to add.

Best regards,

José Braga

 

Thanks

Regards

--
You received this message because you are subscribed to the Google Groups "LSTS Toolchain" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lsts-toolchain+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/lsts-toolchain.
To view this discussion on the web visit https://groups.google.com/d/msgid/lsts-toolchain/ab4af3d0-c0cc-48ae-a27b-4242a6e19747%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Onur Guzel]

Hello

Dear Jose Braga and Jose Pinto, thank you very much for your time and replying my questions. You both really opened my mind about namings and other stuff I asked. I am really glad :)

I am going to work on those new systems and documentations.

Regards