Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Roadmap #1

Open
lowrank opened this issue Sep 10, 2017 · 2 comments
Open

Roadmap #1

lowrank opened this issue Sep 10, 2017 · 2 comments

Comments

@lowrank
Copy link
Owner

lowrank commented Sep 10, 2017

rte solver in 2D only has 1 directional dependence, it is easy to handle the integration over velocity space.

For the meshes, unstructured mesh can be used directly from femm. Or just copy the relevant part of code and paste here.

For ray tracing, the geometry information has to be stored in prior. Storage efficiency needs to be considered.

@lowrank lowrank self-assigned this Sep 14, 2017
@lowrank
Copy link
Owner Author

lowrank commented Sep 19, 2017

geometry stored now. In order to sustain efficiency, it is not good to export them?

update: export the variables will duplicate the memory, in matlab, the parallelism for such tracing algorithm is not perfect yet.

@lowrank
Copy link
Owner Author

lowrank commented Sep 16, 2018

Back to this roadmap, Huh.

now, geometry is stored in a very old-fashioned way, storage almost doubled. Exporting is not necessary for normal computing, but it will be useful to serialize when computing with large data, saving globs will be necessary.

@lowrank lowrank added this to To do in Stage 1 Sep 16, 2018
@lowrank lowrank moved this from To do to In progress in Stage 1 Sep 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Stage 1
  
In progress
Development

No branches or pull requests

1 participant