Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
N
navipy
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Container Registry
Model registry
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Olivier Bertrand
navipy
Commits
d5bbe919
Commit
d5bbe919
authored
6 years ago
by
Olivier Bertrand
Browse files
Options
Downloads
Patches
Plain Diff
Add config file for yaml
parent
37bc37fc
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
navipy/resources/configs/BlenderRender.yaml
+17
-0
17 additions, 0 deletions
navipy/resources/configs/BlenderRender.yaml
todo
+3
-35
3 additions, 35 deletions
todo
with
20 additions
and
35 deletions
navipy/resources/configs/BlenderRender.yaml
0 → 100644
+
17
−
0
View file @
d5bbe919
#
# Default configuration file used by BlendRenderer
#
BlenderRender
:
fov
:
-
min_elevation
:
-90
-
max_elevation
:
90
-
min_azimuth
:
-180
-
max_azimuth
:
180
resolution
:
-
nbpx_azimtuh
:
360
-
nbpx_elevation
:
180
gaussian
:
-
gaussian_width
:
1.5
cycle
:
-
samples
:
30
\ No newline at end of file
This diff is collapsed.
Click to expand it.
todo
+
3
−
35
View file @
d5bbe919
0001: Work on mcode.py
1. Create a new branch (mcode) to work on this (We need to learn how to use those :) )
- see : https://www.atlassian.com/git/tutorials/using-branches/git-merge
2. processing/mcode should contains method based on optic flow
- write geometrical_optic_flow(scene, viewing_directions, posorient_vel):
See the matlab optic flow toolbox of the lab / the stuff you wrote a while ago :)
scene, viewing_directions -> processing/pcode/pcv
posorient_vel should be a pandas series with 'x','y',... 'dx','dy', .... see moving/agent
- write emd_hasenstein_reichardt(scene, prev_response, filters_cutoff)
See Egelhaaf 1989
Should only work for ibpc
- write emd_barlow_lewick(scene, prev_response, filters_cutoff)
See
3. write test functions (like always :) )
- for geometrical optc flow
- yaw only -> no el optic flow
-> az optic flow is prop to sin(el)
- pitch only -> min optic flow at az=+/- 90deg, el=0
- ....
- forward x -> min forward/backward, max on the sides.
4. merge branch mcode with master
0002: Update the doc, massively with
Scheduled : 11/12 of January
0003: Write a new rendering module based on Panda3D (branch panda3d).
0004: Write network like code function (branch ncode)
0. Think on code structure (trying to avoid massive formating)
1. Familiarity network of Bart Baddeley (2012)
2. Haffenbach (1987)
3. Ring-attractor (Goldschmidt 2017)
4. Ring-attractor (Stone 2017)
0005: Change output of comparing to be consistent with place code
\ No newline at end of file
blendrender_traj:
* check how to call exec function with blendnavipy wrapper
* write configuration default file for rendere, and explain how to use it.
\ No newline at end of file
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment