naveenoid / jointOffsetCalibInertial

Algorithm for calibrating joint offsets using inertial measurements

0 stars 2 forks source link

Dev Process discussion #1

Open nunoguedelha opened 8 years ago

nunoguedelha commented 8 years ago

I suggest we set here some aspects of the dev process, like for instance some naming convention for the branches we will be pushing to this repo. I'm listing in this first message the topics of further discussions (list to be populated). We can check the boxes once we finished the discussion on a topic and agreed :

[x] branch naming conventions
[ ] data import folder (and source)
[ ] ...

nunoguedelha commented 8 years ago

branch naming convention

We could use as branch names :

"feature/" for any change on the feature code (function, script)
"debug/" for debugging purposes or adding dummy example/testing data
"fix/" for fixing issues

I use this naming convention to spot faster the relevance of my changes once the repo and number of branches starts growing. @naveenoid feel free to suggest anything else you would find better.

naveenoid commented 8 years ago

Agree fully with branch naming conventions :+1: Another problem which we must already consider is how we import the robot data for analysis..Presumably we are going to be having several data folders (from several different experiment trials) and ideally none of that stays on github. We have some data repositories in IIT iCub Facility, maybe we use them. Maybe you can talk to the other guys and Brunettini to figure this out?

nunoguedelha commented 8 years ago

I hadn't seen your reply update here. Apparently, if you edit a previously submitted comment, Github doesn't send any notification to Slack... Well, I'll ask the guys about the data. I have some data I captured while doing a simple right leg swing, just for checking the capture procedure. I can import that to Slack for now if it's ok for you. Each log file (stateExt/o->data.log or inertialMTB->data.log are around 2Mb large.