git pull origin ramp-marshall-base
remote: Counting objects: 37, done.
remote: Compressing objects: 100% (16/16), done.
remote: Total 29 (delta 12), reused 8 (delta 6)
Unpacking objects: 100% (29/29), done.
From gitorious.org:~omega95/fg/omega95s-fgdata
* branch ramp-marshall-base -> FETCH_HEAD
Auto-merging Nasal/ramp_marshall.nas
git push origin ramp-marshall-base
error: src refspec ramp-marshall-base does not match any.
error: failed to push some refs to 'git@gitorious.org:~omega95/fg/omega95s-fgdata.git'
git checkout ramp-marshall-base
<signal>
<name>eng_start</name>
<type>nasal</type>
<script>
# Nasal Script here
</script>
</signal>
And when the function is eng_start, it should run the nasal script. :)
Philosopher wrote:omega95 wrote in Thu Aug 08, 2013 3:41 pm:Sorry this is out of topic, but behold the flying turtle!
But if you do need to compile a Nasal bit of code, use compile() - compile(str[, name]) generates a func who's contents are str (like func {*str} if you could use the *-prefix operator to embed the contents of the string into the code), and then you call that (you can use call(func[, arg[, me[, namespace[, var err = []]]]]) to call it in a specific namespace, or just a regular function call it in it's own namespace).
var string = " print('hello'); "
var code = compile(string);
code();
there isn't a condition xml tag yet but I'm thinking of making one. Then a user can add signals by only playing with the xml file.
If it has a <wait> then:
omega95 wrote in Thu Aug 08, 2013 5:48 am:Hmm, so you said you don't want to mess with the thumb and fingers. I wanted it to be able to do a thumbs up so I made a thumbs up model and we coud just hide the hand with the wand, both the wands on the other hand and show the thumbs up but it didn't seem to be worth the troubles, form the ICAO annex 2, you can just put the right wand up over your head to signal that everything's ok.
omega95 wrote:So, other than the hands, what joints are you talking about? I understood 3 axes on the wrist = 1joint. Do you need anymore axes on the other joints (shoulder ane elbow)? I think the elbow is fine because humans can only flex their elbow in 1 axis. For the shoulder, we could put a y-axis too.
omega95 wrote:And what are your your thoughts on using xml to store the marshaller's signals and sequence? I think it would limit some options but might some people find that easier to use? For example, in an xml file, we can have positions and sequences...
...
And define a fixed system to parse sequences. Again like I said, this won't give us the freedom nasal does to define sequences...
# check for front gear anytime _nlg_offset is set to zero
if( me._nlg_offset == 0 )
{
me._nlg_offset = 0.01; # ensure it does not stay 0
# get distance of nose wheel to center
# we assume that the foremost gear is the nose landing gear
for(var i = 0; 1; i += 1)
{
var n = props.globals.getNode("/gear/gear[" ~ i ~ "]");
if( n == nil )
break;
if( !n.getValue("wow")
or n.getValue("position-norm") != 1.0 )
continue;
var x = n.getValue("xoffset-in") * IN2M;
if( x > me._nlg_offset )
me._nlg_offset = x;
}
}
Users browsing this forum: No registered users and 2 guests