Skip to content

Documentation for gLayout - #111

Open
Nimok15 wants to merge 12 commits into
ReaLLMASIC:mainfrom
Nimok15:Nimok15-ReadMe
Open

Documentation for gLayout#111
Nimok15 wants to merge 12 commits into
ReaLLMASIC:mainfrom
Nimok15:Nimok15-ReadMe

Conversation

@Nimok15

@Nimok15 Nimok15 commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@msaligane

Copy link
Copy Markdown
Member

@LuighiV

Comment thread README.md
Glayout is a powerful layout automation tool that generates DRC-clean circuit layouts for any technology implementing the Glayout framework. It is implemented as an easy-to-install Python package with all dependencies available on PyPI.

Key features:
- PDK-agnostic layout generation

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure if required to change - by * as they are equally valid for markdown

Comment thread README.md

### Basic Installation

```bash

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think is better defining the language for the highlighting. Not sure why this needed to be deleted.

Comment thread README.md
python tests/sim/run_cell_sim.py --pdk sky130 --all

# Results land in lvs_results/ and sim_results/
```

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pending to add the CI for simulation. Maybe this is better to merge befor the sim CI is approved.

Comment thread README.md
[`tests/sim/testbenches/`](tests/sim/testbenches) and the pass criteria in
[`checks.json`](tests/sim/testbenches/checks.json).

<!-- TODO: replace the values below with the numbers from your latest CI run -->

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will be a good addition for automatic checks. I've seen that in other repos, but not sure how to implement. Maybe good to research it.

return df_in.flatten()

def diff_pair_netlist(fetL: Component, fetR: Component, pdk: Optional[MappedPDK] = None, dum_net: Optional[str] = None) -> Netlist:
def diff_pair_netlist(fetL: Component, fetR: Component, pdk: Optional[MappedPDK] = None, dum_net: Optional[str] = None, substrate_tap: bool = True) -> Netlist:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are these changes required as part of the documentation PR? maybe we can split it in another PR to keep focus just in documentation.

Comment thread sphinx/generators.rst
* - ``guard_ring``
- Well/substrate isolation ring around an arbitrary bounding box
* - ``tapring``
- Tap ring for latch-up prevention

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is mising the resistor, the mimcap and the bjts

@LuighiV

LuighiV commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Hi Prof. @msaligane @Nimok15

I've reviewed the PR. I think it looks great. Just a few comments about:

  • Maybe limit the changes that are concerning to documentation and left others for another PR.
  • I like the idea of live checks, however, I'm pretty sure there is a way we can make this live in the same documentation webpage instead of needeed to check another page. This may require some work with js, but I think is feasible, and might not need to switch to another link to actually check the status.
  • The them looks clean. TBH, I haven't seen it before. However, it could be great if the font size for the left and right side panels would be a little bigger, as it is not noticeable. Side note: the documentation of API are show as tables and not sure if that is the more efficient way. I like a little bit more how gdsfactory theme handles it: https://gdsfactory.github.io/gdsfactory/api/
  • The documentation comments about CI for sims, however, as it was not deployed yet, maybe better waiting for the sim CI before merging this one.
  • I think there is a pending point on the jupyter notebooks. I think there is a plugin to import them into the webpage. Although it could be another PR.
  • Although the notebooks are great, I think could enhance the adoption of the framework if we can add more documentation on how to start using it (with images like gdsfactory).
  • There are missing primitives in the documentation list like resistors, mimcaps, and bjts.
  • Try to don't duplicate information. For contribution page we may use the already guide created by Anhang: https://github.com/ReaLLMASIC/gLayout/blob/main/docs/contributor_guide.md

In general I think it is in a good shape, but maybe is good a second look perhaps from @AL-255. I'd also may recommend checking the pydata-sphinx-theme (used by gdsfactory) instead just to see the difference.

Thanks,
Luighi

@LuighiV

LuighiV commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Just another comment, maybe the documentation files should live under docs folder instead of sphinx

@LuighiV

LuighiV commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Just an update: seems that gdsfactory uses zensical, which is another static documentation site generator, different than sphinx. It looks interesting, however, not sure if worth changing to it.

Something interesting it has is the interactive block execution by readers: https://zensical.org/docs/setup/extensions/markdown-exec/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants