That appears to be to just be a display error on the argument units by the measure writer. Looking through the measure.rb it does appear that the "window_height" argument is used as a length in meters as shown below.

#loop through exterior zones adding ZoneVentilationWindStackOpenArea object
used_exterior_zone_names.sort.uniq.each do |used_exterior_zone|  

  #IDF object text for ZoneVentilationWindStackOpenArea
  string_objects << "
  ZoneVentilation:WindandStackOpenArea,
  #{used_exterior_zone}_WindStack,         !- Name
  #{used_exterior_zone},     !- Zone Name
  #{open_area},              !- Opening Area {m2}
  Always On Discrete 1 WindStack,    !- Opening Area Fraction Schedule Name
  autocalculate,           !- Opening Effectiveness {dimensionless}
  0,                       !- Effective Angle {deg}
  #{window_height},       !- Height Difference {m}
  autocalculate,           !- Discharge Coefficient for Opening
  #{min_indoor_temp},        !- Minimum Indoor Temperature {C}
  ,                        !- Minimum Indoor Temperature Schedule Name
  #{max_indoor_temp},                     !- Maximum Indoor Temperature {C}
  ,                        !- Maximum Indoor Temperature Schedule Name
  #{delta_temp},                    !- Delta Temperature {deltaC}
  ,                        !- Delta Temperature Schedule Name
  #{min_outdoor_temp},                    !- Minimum Outdoor Temperature {C}
  ,                        !- Minimum Outdoor Temperature Schedule Name
  #{max_outdoor_temp},        !- Maximum Outdoor Temperature {C}
  ,                        !- Maximum Outdoor Temperature Schedule Name
  #{max_wind_speed};                      !- Maximum Wind Speed {m/s}
  "
end

You can comment on the measure on BCL, but I don't think authors get any notifications about comments, so we can contact them, since as a BCL moderator we have their contact info.