Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
bprather authored Jan 9, 2025
1 parent b6ce6bc commit 104d062
Showing 1 changed file with 2 additions and 4 deletions.
6 changes: 2 additions & 4 deletions iris/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,6 @@

Iris is a ray-tracer built alongside KHARMA, using Kokkos and Parthenon. Currently it is only useful for imaging KHARMA files: it can produce unpolarized and polarized images at radio frequencies comparable to e.g. Event Horizon Telescope observations, and performs within expected variance compared to other polarized ray-tracers in the polarized comparison problems (i.e. the thin disk and sample dump).

However, it is written to be adapted to many other cases, e.g. automatic flux fitting, multiple cameras and frequency bundling, and eventually Monte Carlo spectra.
However, it is written to be adapted to many other cases, e.g. automatic flux fitting, multiple cameras and frequency bundling, and eventually Monte Carlo spectra and inline imaging as simulations are run.

Iris owes its existence to/uses a lot of code from/shamelessly rips off [ipole](https://github.com/AFD-Illinois/ipole). A few

Code from `ipole` is used under the BSD 3-clause license, and Iris is provided with KHARMA under the same license. I also copied the ipole log/text output format, so anything relying on that for parsing should work fine.
Iris owes its existence to/uses a lot of code from/shamelessly rips off [ipole](https://github.com/AFD-Illinois/ipole). Code from `ipole` is used under the BSD 3-clause license, and Iris is provided with KHARMA under the same license. I also copied the ipole log/text output format, so anything relying on that for parsing should continue to work with iris.

0 comments on commit 104d062

Please sign in to comment.