DAEHYUN KIM

Get a list of unplaced cells: (Laurent Lefebure)
    dbGet [dbGet -p top.insts.pStatus unplaced].name

See what metal layers your block's IO pins are on: (Bob Dwyer)
    dbGet top.terms.pins.allShapes.layer.name

Get a list of NONDEFAULT rules in the design: (Gary Nunn)
    dbGet head.rules.name

Get the placement status of an instance: (Ali Aslani)
    dbGet [dbGetInstByName instName].pStatus

Get the points of a rectangular routing blockage: (Bob Dwyer)
    dbGet top.fplan.rBlkgs.shapes.rect

Get the points of a rectilinear routing blockage: (Jon Cooper)
    dbGet top.fplan.rBlkgs.shapes.poly

Get a list of all cell types used in the design: (Gary Nunn)
    dbGet -u top.insts.cell.name
    (The "-u" filters out duplicate objects.)

Get the size of block placement halos: (Kari Summers / Bob Dwyer)
    dbGet [dbGet -p2 top.insts.cell.subClass block*].pHaloTop
    dbGet [dbGet -p2 top.insts.cell.subClass block*].pHaloBot
    dbGet [dbGet -p2 top.insts.cell.subClass block*].pHaloLeft
    dbGet [dbGet -p2 top.insts.cell.subClass block*].pHaloRight

Get the size and top/bottom layers of block routing halos: (Bob Dwyer)
    dbGet [dbGet -p2 top.insts.cell.subClass block*].rHaloSideSize
    dbGet [dbGet -p2 top.insts.cell.subClass block*].rHaloBotLayer.name
    dbGet [dbGet -p2 top.insts.cell.subClass block*].rHaloTopLayer.name

Make sure all your tiehi/lo connections have tie cells (and are not connected to a rail instead): (Gary Nunn)
    dbGet top.insts.instTerms.isTieHi 1
    dbGet top.insts.instTerms.isTieLo 1
    (Should return "0x0" if all connections have tie cells.
     If "1"s are returned, use the following to find the terms that still need a tie cell:)
    dbGet [dbGet -p top.insts.instTerms.isTieHi 1].name
    dbGet [dbGet -p top.insts.instTerms.isTieLo 1].name

Change the routing status of a net (for example, from FIXED to ROUTED): (Gary Nunn)
    dbSet [dbGet -p top.nets.name netName].wires.status routed

Get the status of your design: (Siva Kumar)
    dbGet top.statusIoPlaced
    dbGet top.statusPlaced
    dbGet top.statusClockSynthesized
    dbGet top.statusRouted
    dbGet top.statusRCExtracted
    dbGet top.statusPowerAnalyzed

List all the FIXED instances in your design: (Bob Dwyer)
    dbGet [dbGet -p top.insts.pStatus fixed].name

Find out which layers are used in a net: (Bob Dwyer)
    dbGet [dbGet -p top.nets.name netName].wires.layer.name

Find all the instances of a certain cell type: (Laurent Lefebure)
    dbGet [dbGet -p2 top.insts.cell.name cellName].name

Get the size of a cell in the library, but not necessarily in the current design: (Rob Lipsey)
    dbGet [dbGetCellByName cellName].size

I'm sure there are many more useful dbGet/dbSet one-liners out there; let's hear yours! Please post in the comments some of the dbGet lines that you have come up with.

Related Resources:

Biophysical Neural Network Simulator

<Only Inference>

1. Simulation Run

>> ./home/dkim785/Tools/CUDA/INF_Neuron_Simulatior_HPC/Debug/Run the INF_Neuron_Simulator_HPC

2. Type '8'

3. Run the Matlab Code (/home/dkim785/Tools/CUDA/INF_Neuron_Simulator_HPC/Debug/mass_process_read_potential_2.m

4. Symulation Run and Type '7'

5. You can see the result.

<How to change the parameters?>

1. For the first try, I changed the 'Debug/device2_output_network.txt'.

2. Just copied it, and open.

3. Inside this file, you can see the parameters, and weights.

4. Order is (This neuron's number // 2 // LIF_b // LIF_th // LIF_reset // 20.000000 // LIF_c // LIF_a // -65.060000 // 0.000 // 0.000 ; From, Weight, From, Weight ...)

5. Change the parameters.

6. If it is not work, we should change the weights. (You should learning)

<Learning>

1. Run the INF_Neruon_Simulator_HPC

2. Type '4'

Yun's Matlab Simulator

< Yun's Code>

1. Check the parameters by run model_compare_tuned.m

2. Inside the model_compare_tuned.m code, there is

1. Basic principles

2. Micro-level (sentences)

-> 대부분의 시간을 여기에 쓸 것임.

3. Meso-Level (paragraph)

4. Macro-level

* Coherence(일관성) -> Logical

* Selection of ideas. 어떤 정보가 포함되고, 배제될 것인가?

* Organization of ideas. 

* Cohesion(결합) -> Connection

* How are ideas linguistically connect to one another?

* 4 Different way to make cohesion

* Repetition

* Repetition: Exact Word

* ~~ materials, materials ~~

* Repetition: With a difference

* ~~to increase~~. ~~ increasing ~~. ~~increase~~

* Repetition: Synonym or Other Words Representation

* This ::article:: does not ~~, nor is ::it:: a compare~~. Rather, the following ::text:: identifies ~~.

* 무엇이 가장 흔한가? -> Repetition: Exact Word.

* Transition words or phrases (So, Therefore, However, etc…)

* Linking Words (List가 Canvas에 업로드 되어 있음)

* Conjunctions

* Punctuation (:, ;)

* 얘들은 cohesive type of device inside the sentence.(Micro-level)

* Parallel Structure

* such as (i) promoting ~~; (ii) allowing ~~; (iii) offering ~~. 이렇게 하면 3가지에 대해 이야기하고 이 세가지가 모두 동등하다는 것을 알 수 있음.

-> 그렇기 때문에, good coherence + bad cohesion과 vice versa is possible.

이것 둘 다 좋도록 신경써야 한다.

* 3 Types of information

* Primary Info (메인 주제, 내가 한 것)

* ‘::we::’, ‘::our research::’ 을 쓰면서 이야기.

* ‘::This may be an issue of:: XYZ ::but may also be more telling about:: ABC

* ::Hence, understanding:: XYZ ::can help provide:: ABC

* 위와 같은 것을 쓰면 primary info라는 것을 알려줌.

* Secondary Info (다른 사람들 것을 refer)

* Reference 쓰고 [1] 이런것 쓰면 됨.

* Common Knowledge 

* 나나 다른사람의 research에 대한 것은 아니지만, 모든 사람들이 common sense로 알고 있는 것. 예를 들어서 Smoking 은 Cancer를 유발한다. 예전에는 리서치였겠지만 요새는 그냥 common knowledge

-> Reader가 이 세가지를 모두 한 눈에 구별하면서 읽을 수 있도록 해야 한다. 그렇지 않으면 plagiarism이 될 수 있다.

- HW - 메일로 받은 자료에 highlight 하기.

Yellow: Secondary Info

Green: Common Knowledge

Primary Info는 냅두기.