attractor | code complexity metrics visualization and exploration tool

The problem is that the formula for orbital speed is used to derive the speed of an object in orbit, but you're using it as a form of constant thrust applied to each body towards each other. That's a bit like calculating the speed of a moving car, and then applying the same speed back to it as an impulse!

The only force experienced by objects in orbit is the one you get from Newton's law G * m * m / r*r. In order to actually orbit though, the planets will need an initial velocity - this can be calculated from the orbital speed formula. Calculate it at the given distance, and apply it on Start() in a direction perpendicular to the orbital plane and the direction to the sun (or whatever you want to orbit), you can get this from dir = Vector3.Cross(sunDir, Vector3.up).normalized

Note that gravitational systems are not numerically stable in physics engines relying on euler integration (such as PhysX). You need things like Runge-Kutta integration for that, or the planets will eventually lose their orbit if you leave the simulation running for long enough.

The pedWait block has that option clearly defined: you can choose a customer attractor choice and use areaNode local variable in the attractor choice in order to get the attractor you want. In this example i choose the first attractor (with index 0), but you will have to create your own logic in order to decide what is the suitable attractor for your incoming agent.

YOu have to manually tell it to which attractor it should go. Attractors are not actual physical spaces (that become "full" if something is stored there). They are just spaces to separate things visually.

In your process blocks, you probably did not specify the attractors correctly or did not define to move to a random attractor. But even in the latter case, you could have things being stored in the same attractor.

Two options:

1. Either, turn your attractors into actual agents with rectangular nodes, that you setup to be "empty/full" with state charts (faster but harder to design)
2. Or use the material handling library with its storage system setup, doing this for your (but this is computationally slower)

Not in OMEdit as far as I am aware. However, one alternative is to use the.csv or .mat file and use some auxiliary tool such as GNUPlot or some other plotting tool.

You can change the output here:

The resulting file will be in the working directory of OMEdit:

In LEC_system(u), the flat vector u contains in sequence

• the state vector, n components,
• the eigenbasis U, a n x n matrix
• the accumulated exponents L, n components.

With n=4, this translates thus to the decomposition

You should be able to use pedWait.free(randomFrom(pedWait.getPeds())); . This will remove a random ped from the block.

Learn how to use code-complete and how to understand the options you have. The free() method wants to know exactly which ped to free, so you need to tell it. In the example above, we grab a random Ped from it.

Pedestrians cannot "sit still". As soon as they sense someone else close by, they "get nervous", based on how their collision avoidance is working internally.

If you have to freeze them, one way would be to convert them to normal agents once they arrive at their destination (and re-convert into Peds once they need moving).

Check the help as convert agents into different types is a useful skill that is applied a lot normally. Also saves you performance (no need to do Ped stuff to agents that just sit around)

Yes.

Easiest way is to use Enter and Exit blocks in Main and your agent types and send the agents across different spaces this way. In the Enter properties, specify a location within the agent type and it will make your arriving agent "switch" to the new space.

If you are not using process modelling blocks, you need to call setEnvironment() and then define the agent location within its new environment using setLocation(...)

simple... go to the project panel and select all of them as shown in the following image... then click on create collection