Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Glayout Restructure #307

Closed
wants to merge 28 commits into from
Closed

Glayout Restructure #307

wants to merge 28 commits into from

Conversation

chetanyagoyal
Copy link
Collaborator

@chetanyagoyal chetanyagoyal commented Jun 5, 2024

Implements the following folder structure

  • glayout/flow

    • primitives
      • fet.py
      • mimcap.py
      • guardring.py
      • resistor.py
      • via_gen.py
    • blocks
      • diff_pair
        • diff_pair.py
        • init.py
        • spice netlist
      • opamp
        • ...
      • ...other larger blocks
    • regression
      • drc
        • ...drc report folders
      • lvs
        • ...lvs report folders
      • testbenches
        • ...component spice testbench results
    • pdk
    • spice
    • placement (contains placement methods)
    • routing
  • the idea for the empty regression folder is to store drc, lvs and spice testbench reports there

  • the drc and lvs functions have been adapted so that

    • they create a folder named {design_name} in the respective drc, lvs or testbench folder
    • store the report file in that folder

chetanyagoyal and others added 26 commits May 25, 2024 12:16
2. swap plus and minus pins in add pin labels function for opamp
3. modify error logging in drc and lvs for glayout
4. create yaml workflow file for glayout
5. add pip install glayout from git commands for later use
delete unimportant copy of glayout parser script in generators/glayout folder (is copied from .github/scripts)
2. regression test for current mirror
3. cap off drc lvs for components
@chetanyagoyal
Copy link
Collaborator Author

[IMPORTANT]: @msaligane the branch 'no_top_components' of the source repo has another tentative folder structure, which might be a better idea

@chetanyagoyal
Copy link
Collaborator Author

@msaligane @alibillalhammoud , the conflicts have been resolved as best they can, but github won't recognise it due the folder changes

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.

1 participant