docs(specs/opat): updated opat spec for general indexing
OPAL type II tables use a 4 vector for composition, while many other opacity tables use a 2 vector of composition to index tables. In an attempt to be as general as possible I have updated the OPAT specification to allow for tables indexed by a vector of any length [1, 255]. This should allow a single spec to be used when storeing and accessing type I or type II tables. BREAKING CHANGE: Careful thought will have to be given to how the C++ module handles this. We want the same code to work for querying data from any kind of opaticy table
This commit is contained in:
BIN
specs/OPAT/._OPAT.pdf
Executable file
BIN
specs/OPAT/._OPAT.pdf
Executable file
Binary file not shown.
BIN
specs/OPAT/OPAT.pdf
Normal file → Executable file
BIN
specs/OPAT/OPAT.pdf
Normal file → Executable file
Binary file not shown.
Reference in New Issue
Block a user