It would be awesome and provide to your doc a fresh user-friendly experience. For example, slate.js have done it and it is awesome, you can easily find your features and go from one place to another, so... here my feature request, what do you think about that :)?

I think it's unexpected. I have to use Detector.canCollide on my own when I want to use Query.collides. I think it should be changed or at least mention in documentation.

I see the "Welcome" doc page mentions "component system", but it is very vague. Can you describe what are all the reasons that I'd want to use Whitestorm over plain Three.js, f.e. what are all the things I get that Three.js does no offer, so that I can better understand?

Thanks!

from World.js

/**

• Add a spring to the simulation
• @method addSpring
• @param {Spring} spring
  */
  World.prototype.addSpring = function(spring){
  this.springs.push(spring);
  var evt = this.addSpringEvent;
  evt.spring = spring;
  this.emit(evt);
  evt.spring = null;
  };

/**

• Remove a spring
• @method removeSpring
• @param {Spring} spring
  */
  World.p

Failed to execute 'requestFullscreen' on 'Element': API can only be initiated by a user gesture.

Probably should use game.input.onUp instead (photonstorm/phaser-ce#27).

The tutorial at
https://www.nphysics.org/joint_constraints_and_multibodies/

has a line says

let joint = RevoluteJoint::new(-0.1);

While the new signature is pub fn new(axis: Unit<AngularVector>, angle: N) -> Self

To maximize performance across all devices, memory should be pre-allocated for any per-frame op in the worker

The evaluation service related code has a dependency on msgpack and msgpack_numpy (reference : https://github.com/stanfordnmbl/osim-rl/blob/master/osim/redis/service.py#L7) which should be added as a dependency in setup.py

We should also probably make a release after adding the same, as many submissions are failing because of lack of msgpack and msgpack_numpy

We have quite a few common booleans we use in many places of the code.
Some of them are very simple, like checking for compressible vs incompressible, or for FSI.
But when we want to express something more complicated like is it SA or SST, is the mesh moving or deforming, is this FEM or FVM or FEA, and so on, things are not so simple anymore and we end up with long conditionals repeated in many

The documentation for properties in psi4/driver/driver.py does not currently include the dipole/quadrupole/traceless quadrupole polarizability capabilities that were implemented.

Currently the output at runtime produces, for instance, the following:

PIConGPUVerbose PHYSICS(1) | Courant c*dt <= 1.66765 ? 1
PIConGPUVerbose PHYSICS(1) | species e: omega_p * dt <= 0.1 ? 3.56797e-08

The way the output is formatted I interpret it as a "question to the code", i.e., "Is c*dt <= ?" To which a natural answer would be "Yes/No" or "True/False" and not

Hello,

There seem to be an issue in template recognition when creating mappings involving Rigid3d DoFs.

Namely, when creating a BarycentricMapping or a BeamLinearMapping between a mechanical model and a collision model of connected beam elements, I receive the following error messages:

`[ERROR] [InfoComponent(Not created (BarycentricMapping))] Object type BarycentricMapping<Vec3d,Rigid3