hugoguillen/refractiveindex.info-sqlite

SQLite wrapper for the refractiveindex.info database.

refractiveindex.info-sqlite's Issues

Changed format of refractiveindex.info data

Hi,

the data structure of the refrativeindex.info yaml library that is available at there website has changed. This requires some minor changes in the refrativeindex.info-sqlite to work with the new format. Are you still maintaining this project and would you accept a PR to fix this?

Best.

Error Handling

Hi,
I stumbled across your sqlite3 wrapper cause I wanted to use the refractive index library
inside a plugin for a physical calculator I am currently developing. (https://gitlab.com/lyding/hfcl)
Therefor I would like this library to get rid of its verbose character. Currently vital information
and error messages are printed directly to the console which makes it unusable as library within a project.
Would you be interested in me adding a more meaningful error handling?
Of course I would stay backward compatible.

Kind regards,
lyding

Cant load all materials correctly

Hi,
I started to add error handling using custom exceptions.
During this I realized that some of the Exceptions in material.py are constructed
but not raised. So they where never active. After raising them I tried to recreate
the database which yielded that two materials could not be loaded:

LOG: 800,organic,polyvinylpyrrolidone,Konig : Invalid yaml material file
LOG: 2687,3d,plastics,pvp : Invalid yaml material file
***Wrote SQLite DB on refractive.db

The exception is raised from the constructor of the Material class in line 64
which was inert before cause of a missing raise statement.
I inspected the Koenig.yaml file:

DATA:

• type: formula 5
  wavelength_range: 0.375 1
  coefficients: 1.5151 0.00279 -2 5.0756E-4 -4
• type: tabulated nk
  data: |
  ....

It seems that this YAML file provides two different refractive index data.
I checked out the refractiveindex.info page and itt seems that they are using the formula
to interpolate the refractive index. I would change the loading code so it also prefers to formula
data over the tabulated data if both are given, or do you see a reason to do otherwise?