Database

[joamatab]

• add database for structured data for simulations and measurements

@tvt173
@flaport
@thomasdorch
@SkandanC
@proppy

[codecov]

Codecov Report

Merging #990 (a075b87) into main (e9552e8) will increase coverage by 0.25%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #990      +/-   ##
==========================================
+ Coverage   74.08%   74.34%   +0.25%     
==========================================
  Files         433      434       +1     
  Lines       22217    22442     +225     
  Branches     2985     2985              
==========================================
+ Hits        16459    16684     +225     
  Misses       4871     4871              
  Partials      887      887              

Impacted Files	Coverage Δ
gdsfactory/database/models.py	100.00% <100.00%> (ø)
gdsfactory/components/terminator.py	100.00% <0.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[tvt173]

would be great if we can generate a diagram of the database to review
https://crashlaker.github.io/database/2020/05/13/database_diagram_with_python_sqlalchemy.html

[joamatab]

Here is a diagram

[joamatab]

I can merge it and then we can add documentation on how to add data to it into future PRs:

TODO:

• add examples on how to add and query measurements and simulations
• add examples on how to bring up and connect your own database

Maybe:

• Include GDS serialization (polygons and references)
• material database

[tvt173]

hi @joamatab , overall it looks good to me. the only part I have any immediate criticisms for are the port type:

you have is_electrical and is_optical as columns, but I think it would be cleaner and more flexible to have something like port_type which is either a string or maps to a table of port types. what do you think?

also, do you have or see value in adding a relation to a PDK name/version used to make the wafer? or otherwise to the version of the code used to generate it?