Giter VIP home page Giter VIP logo

bromium's People

Contributors

bergwerf avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

Forkers

johnjohndoe

bromium's Issues

Migrate to unsigned 32 bit integers for particle positions

Until now there have been two ways to represent the particle position: unsigned 16 bit integers and 32 bit floats. The floats were originally there to allow simulations with more precision, however, they have added a lot of complexity and confusion to the code. The 3 x uint16 positions were originally intended to represent a voxel position so the particle position does not have to be converted to a voxel position every step (note that uint16 is almost the largest type that is suitable for this because the voxel position and type have to be hashed into a 64 bit integer). However, to keep things simple we're going to move to unsigned 32 bit integers. The ability to omit voxel position computation and particle distance computation (by using voxel groups instead of square roots) can still be maintained by setting each voxel to contain only one particle position. Voxels can also contain more particle positions to increase precision.

Implement extensive benchmarking

Benchmarking should support the following features:

  • Integrate into the computation engine for live benchmarking
  • Keep old benchmarks in the repository to measure progress
  • Run with dart2js and d8 for realistic JavaScript benchmarks

Change float32/uint16 distinction to point/voxel distinction

Although float32 is the underlying type to store exact particle coordinates and uint16 is the underlying type to store voxel positions. It is more straightforward if all functions that are specialized to handle a specific type are named using this point/voxel distinction. Example: Domain.containsPoint and Domain.containsVoxel instead of Domain.containsFloat and Domain.containsUint16. The BromiumData.useIntegers boolean and related namings should be converted to useUint16.

Implement extensive exception reporting

There are many possible exceptions (especially in the fixed data buffer). Therefore there should be a special BromiumException for exception handling within bromium.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.