vitor_a
Newbie

Hi everyone,
My ADS workspace is sometimes disorganized.
I adopted a descriptive string to manage the levels of simulation for each cell:
Circuit_Step_task_version
Example:
Amplifier_00_bias_v1
Amplifier_01_impedance-matching-TLIN-ideal_v1
Amplifier_02_impedance-matching-LAYOUT_v1
Amplifier_02_impedance-matching-LAYOUT_v2
Amplifier_02_impedance-matching-LAYOUT_v3
Amplifier_03_Layout_TB_v1 (TB = testbench --> Circuit co-simulation)
...
Additionally, I take notes on a text file about what is observed on each step.
But sometimes it becomes a little messy, mainly when I create many versions.
The big problem comes up in the co-simulations, because it can have many other sections of the circuits (ex: bias-T, input impedance matching, output impedance matching, filters, etc.)
It would be good to discuss some tips and tricks that could help the design flow and retrieval of results.
Which methodology do you apply to organize ADS workspace?
My ADS workspace is sometimes disorganized.
I adopted a descriptive string to manage the levels of simulation for each cell:
Circuit_Step_task_version
Example:
Amplifier_00_bias_v1
Amplifier_01_impedance-matching-TLIN-ideal_v1
Amplifier_02_impedance-matching-LAYOUT_v1
Amplifier_02_impedance-matching-LAYOUT_v2
Amplifier_02_impedance-matching-LAYOUT_v3
Amplifier_03_Layout_TB_v1 (TB = testbench --> Circuit co-simulation)
...
Additionally, I take notes on a text file about what is observed on each step.
But sometimes it becomes a little messy, mainly when I create many versions.
The big problem comes up in the co-simulations, because it can have many other sections of the circuits (ex: bias-T, input impedance matching, output impedance matching, filters, etc.)
It would be good to discuss some tips and tricks that could help the design flow and retrieval of results.
Which methodology do you apply to organize ADS workspace?