AMCL /scan not recieved but is subscribed

I am running a Gazebo simulation for my robot and trying to use the Navigation Stack. I am trying to get the ACML node to work and am having issues with the /scan topic. The DEBUG info says that there is no laser scan received. I am thinking this is possibly since there are 'inf's in the laser scan topic... Does the ACML localization work with inf (note these are not NaN's) in the laser scan? [Here](https://drive.google.com/file/d/12jbgqw-_J1uwYfbJLupHPmz0jyPCp854/view?usp=sharing) is my rqt_graph. [Here](https://drive.google.com/file/d/1c_36Am9Bi145rPecTc21SmpbgfSqKgDA/view?usp=sharing) is a sample of my /scan topic that the ACML node is subscribing to. move_base.launch (to start the Navigation Stack with ACML node): # using map from the bender model world Here is my common_costmap_params: obstacle_range: 0.5 # the maximum distance without updating the costmap raytrace_range: 3.0 # the range to which footprint: [[-0.40, 0.445], [0.40, 0.445], [0.40, -0.445], [-0.40, -0.445]] # simple box configuration #robot_radius: ir_of_robot inflation_radius: 0.10 # 10 centemeters away from the robot - minimum distance away from an obsticle observation_sources: laser_scan_sensor laser_scan_sensor: {sensor_frame: laser, data_type: LaserScan, topic: scan, marking: true, clearing: true} # marking is adding new things to the costmap. Clearing is clearing obsticles from the costmap Here is my global_costmap_params: global_costmap: global_frame: map # defines what coordinate frame the costmap should run in robot_base_frame: base_link # the coordinate frame the robot should reference as the base of the bot update_frequency: 5.0 # (Hz) static_map: true # should the costmap initialize itself based on a map served by the map_server. # Put this to false if there is not a static map of if there is no map at all Here is my local_costmap_params: local_costmap: global_frame: odom robot_base_frame: base_link update_frequency: 5.0 # (Hz) publish_frequency: 2.0 # (Hz) static_map: false rolling_window: true # Setting to true means that the costmap will remain centered around the robot as it moves around the world width: 6.0 height: 6.0 resolution: 0.05 # These three set the width, height, and resolution of the costmap. Should (but do not have to be) the same as the static map Any help is appreciated!! Thank you.