How to set rot, loc relative to an object and depending of the direction

Question

question

Nicolas Mbz asked Feb 19, '24 Nicolas Mbz commented Feb 19, '24

How to set rot, loc relative to an object and depending of the direction

Hello,
There are different objects (ObjToPos) that can remain on floorspots (patient, bed, gurney, chair). There are several floorspots facing in different directions. I would like these objects

1) are properly centered on the floor spot

2) if possible, that the rotation follows the direction of travel

In the example bellow, Bed1 should be centered on the FloorSpot1 and the Man1 should be centered on the Floorspot2 with the same z rotation of the floorspot

Positionner_Patient_Bed_sur_floorspot.fsm

An idea ? Thanks in advance

Software Version:

FlexSim 23.2.3

visual setlocation setrotation

1708341390995.png (336.9 KiB)

positionner-patient-bed-sur-floorspot.fsm (50.5 KiB)

Answer 1 · 2024-02-19T14:33:22Z

Jason Lightfoot answered Feb 19, '24 Nicolas Mbz commented Feb 19, '24

You can add a travel to location to the floor spot rather then setting the rotation and location yourself.

Using network nodes like this you should connect between the two either side of the location using a D connection, which means it can join the network at the closest node to its onward travel.

Example attached.

positionner-patient-bed-sur-floorspot_jl.fsm

positionner-patient-bed-sur-floorspot-jl.fsm (51.4 KiB)

· 3

Nicolas Mbz commented · Feb 19 at 03:06 PM

Thanks a lot ! It works. That's perfect. 2 subsidiary questions

1) Assign labels
token.FloorSpot.getLocation(0.5,0.5,0).project(token.FloorSpot.up,token.ObjToPos.up)

What is the role of the underlined part ?

2) Where can I find the description of the D connection in the documentation ?
Your explanation is clear, but didn't know that it exists and could be useful to read theory about it.

0 ·

1708354956209.png (21.0 KiB)

Jason Lightfoot ♦ Nicolas Mbz commented · Feb 19 at 03:18 PM

The Vec3 project() method is used here to ensure that the coordinates are in the traveller's space. You could assume they are in the same container/hierarchy in the model but it's safer to write the code generically without that assumption.

You can read more about alternate exits here

0 ·

Nicolas Mbz Jason Lightfoot ♦ commented · Feb 19 at 03:37 PM

Thanks a lot !

0 ·

question