Johan Euphrosine
Johan Euphrosine
@meheff @grebe will https://google.github.io/xls/design_docs/proc_scoped_channels/ help with this? Related #869.
Note currently lowering a proc that accept arrays of channels fails with: ``` Could not extract a textual position from error message: INVALID_ARGUMENT: Expression @ xls/examples/matmul_4x4/matmul_4x4.x:120:36-120:50 was not constexpr: `activations_in`...
Looking at the netlist for sky130 examples here: https://gdsfactory.github.io/skywater130/notebooks/intro.html `get_netlist()` returns the following data structure: ``` {'connections': {}, 'instances': {'sky130_fd_sc_hd__a2111o_1_1': {'component': 'sky130_fd_sc_hd__a2111o_1', 'settings': {}}, 'sky130_fd_sc_hd__a311oi_4_1': {'component': 'sky130_fd_sc_hd__a311oi_4', 'settings': {}}, 'straight_1':...
trying magic `ext2spice` on the resulting gds: ``` gds read test.gds extract ext2spice lvs ext2spice cthresh 0 ext2spice ``` also trigger some interesting `Unknown layer/datatype errors: ``` Magic 8.3 revision...
> You need to connect at least two components using metal routes or connect components directly to each other Looking at the example at https://gdsfactory.github.io/skywater130/notebooks/intro.html I was under the impression...
> for instance like [the Spice notebook](https://github.com/simbilod/gdsfactory/blob/spice/docs/notebooks/plugins/spice/01_voltage_divider.ipynb) where I have a voltage divider. Thanks for sharing, that's awesome! It would be good to try to submit together a small design...
> @proppy : 68:0 is a production mask layer number; it's not supposed to be used for design. For design shapes, you should be using the drawing purpose 68:20 Thanks...
I believe this is now fixed with: ``` openlane 2023.06.26_0_g3bc9d02d 20230606_125334 litex-hub 12MB ``` from https://anaconda.org/LiteX-Hub/openlane/files (see https://github.com/hdl/conda-eda/pull/345 https://github.com/hdl/conda-eda/pull/348)
And there is a bit of a chicken and egg problem when you don't use a fixed port for running the registry. Since you don't know which port will get...
@abourget it also need to be supported in the remote API. Currently docker-py expose an `insecure_registry` flag on the `pull` function, but it's only used to resolve the endpoint: https://github.com/docker/docker-py/blob/master/docker/client.py#L794