PowerMesh

Comments

• Matthias

  February 2021

  Very good

  Much better with the backticks.

  But there is an excess one in the line after "include RBA"

  Matthias
• tagger5896

  February 2021

  Ahhh , just now saw that thanks
• tagger5896

  February 2021

  Matthias,

  Update to process the vias this needs too be cleaned up with respect to the Global definitions and other things as well
  Still Learning ... Baby Steps.
  As its works like I want, there is probably a better way

  Just a thought for all of you out there
  If you want to be a EDA programmer, you should be willing to be the dumbest person in
  the room and embarrass yourself as a noob.
  And you know what, that’s how we improve ourselves.
  I don’t want to be the smartest person in a room.
  That’s the wrong room for me. I want to be surrounded only by smarter people.

  include RBA
  
  $app   = RBA::Application.instance
  $mw   = $app.main_window
  $view  = $mw.current_view
  $cv      = $view.cellview($view.active_cellview_index) 
  $cl       = $view.active_cellview.cell
  $cv      = RBA::CellView::active
  $lay     = $view.active_cellview.layout
  $cell    = $cv.cell
  $dbu    = $lay.dbu 
  $layer_info = LayerInfo.new(10,0)
  $layer_index = $lay.layer($layer_info)
  
  #Build Corrdinate Array Class
  def set(var)
    x = 0
    eval('x=var;')
  end
  
  class Coordinate
        attr_reader :x1, :y1, :x2, :y2
  
    def to_s
          "(#{x1},#{y1},#{x2},#{y2})"
    end
  
    def initialize(x1,y1,x2,y2)
          @x1 = x1
          @y1 = y1
          @x2 = x2
          @y2 = y2
    end
  
    def <=>(other)
         [x1, y1] <=> [other.x1, other.y1]
    end
  
  end
  
  def process_vias
  
      if $view == nil
          raise "Process Vias: No view selected"
      end
  
      $view.transaction( "Process Vias" )
  
      layer_info = LayerInfo.new(10,0)
      layer_index = $lay.layer(layer_info)
      coords = Array.new
  
      $cell.each_shape(layer_index) do |shape|
          if shape.is_box?
              #Convert polygon to Box
              box =  shape.box
              coords.push(box)
          end #end do
          end 
  
      $cord = Array.new
      #Convert RBA:Box class to array
        coords.each { |i|
                lx  =  i.left
                ly  =  i.bottom
                ux =  i.right
                uy =  i.top  
                $cord <<  Coordinate.new(lx,ly,ux,uy)
        }
       $srt = $cord.sort!
       $len = $srt.length()
       $e =Array.new
       $o =Array.new
       $a   =*(0..$len)
       $e  << $a.values_at(* $a.each_index.select {|i| i.even?})
       $o  << $a.values_at(* $a.each_index.select {|i| i.odd?})
      #Flatten array to get Odd/Even Values
       $fe  = $e.flatten
       $fo =  $o.flatten
      #New Array to Store Odd/Even
       $ee =Array.new
       $oo =Array.new
      # puts Slice into 13xN array based on number of rows
       $fe.each_slice(13) { |row| $ee << row.map{|e| e}}
       $fo.each_slice(13) { |row| $oo << row.map{|e| e}}
  
  end     
  
  
  ##############################################
  # Process Even Vias
  #Global  $ee
  ##############################################
  def even_vias     
      if $view == nil
          raise "Process Vias: No view selected"
      end
      # start transaction for "undo"
      $view.transaction( "Process Vias" )
  
  cnt =  $ee.length()
  x = 0
  $ee.each do |via|
     if x.even?
          puts via.join(",")
          #set length to minus 1 to avoid nil
          #Gotta be a better way
          (0..$ee[x].length-1).each  do |en|
          xn = $ee[x][en]
          $x = $srt[xn]   
          $x1 =  $x.instance_variable_get :@x1
          $y1 =  $x.instance_variable_get :@y1
          $x2 =  $x.instance_variable_get :@x2
          $y2 =  $x.instance_variable_get :@y2
          box = RBA::Box::new($x1,$y1 ,$x2 , $y2)
          shapes = $cell.shapes($layer_index)
          shapes.each_overlapping(box) do |s|
          puts  s
            shapes.erase(s)
                  end    
            end
        end
        x += 1
    end
   ensure
      $view.commit
      $view.cancel
  end
  ##############################################
  # Process  Odd Vias
  #Global  $oo
  ##############################################
  def odd_vias     
      if $view == nil
          raise "Process Vias: No view selected"
      end
      # start transaction for "undo"
      $view.transaction( "Process Vias" )
  
  cnt =  $ee.length()
  x = 0
  $oo.each do |via|
     if x.odd?
          puts via.join(",")
          #set length to minus 1 to avoid nil
          #Gotta be a better way
          (0..$oo[x].length-1).each  do |en|
          xn = $oo[x][en]
          $x = $srt[xn]   
          $x1 =  $x.instance_variable_get :@x1
          $y1 =  $x.instance_variable_get :@y1
          $x2 =  $x.instance_variable_get :@x2
          $y2 =  $x.instance_variable_get :@y2
          box = RBA::Box::new($x1,$y1 ,$x2 , $y2)
          shapes = $cell.shapes($layer_index)
          shapes.each_overlapping(box) do |s|
          puts  s
             shapes.erase(s)
                  end    
            end
        end
        x += 1
    end
   ensure
      $view.commit
      $view.cancel
  end
  ##########################################################
  #Process Vias Even/Odd Supplies VDD/VSS or what ever supply
  process_vias
  even_vias
  odd_vias
  ##########################################################
  
• Matthias

  February 2021

  @tagger5896 I agree with your approach. But then, who are the people then who play the smarter ones?

  In general, EDA programming isn't much different from many other fields of programming. It's just that EDA tool coding usually isn't taken to a level where skill makes a difference. EDA users are often content with small scripted solutions that make their life easier. But this thinking bears risks. I've seen projects growing from tiny scripts to monsters beyond maintenance. Real software engineers will try to avoid this at every cost - the keywords being refactoring, architecture and design, continuous integration, test driven development style and so on. EDA programmers often seem to consider this overhead, but it's really worth thinking about a test strategy for example right from the beginning. With this in mind EDA programming should be quite similar to other fields of domain specific coding.

  And maybe with this standard in mind, popular EDA tools might finally offer coding platforms which are better than last millenium style.

  Matthias
• tagger5896

  February 2021 edited February 2021

  Matthias,

  I agree ..