Attempt to interpret non-number value as number src\gas.rs

proc name: auxtools stack trace (/proc/auxtools_stack_trace)
src: null
call stack:
auxtools stack trace("Attempt to interpret non-numbe...")
the disposal unit (/obj/machinery/disposal/bin): LateInitialize()
Atoms (/datum/controller/subsystem/atoms): InitializeAtoms(/list (/list), null)
Kilo Mech Recharger (/datum/map_template/random_room/sk_rdm073): initTemplateBounds(/list (/list), 1)
Kilo Mech Recharger (/datum/map_template/random_room/sk_rdm073): load(the plating (67,105,7) (/turf/open/floor/plating), 0, 1, 1)
3x3 room spawner (/obj/effect/spawner/room/threexthree): Initialize(1)
Atoms (/datum/controller/subsystem/atoms): InitAtom(3x3 room spawner (/obj/effect/spawner/room/threexthree), 0, /list (/list))
Atoms (/datum/controller/subsystem/atoms): CreateAtoms(null, null)
Atoms (/datum/controller/subsystem/atoms): InitializeAtoms(null, null)
Atoms (/datum/controller/subsystem/atoms): Initialize(783008)
Master (/datum/controller/master): Initialize(10, 0, 1)

Start with src\gas.rs and reproduce the error using the supplied stack trace, which passes through the disposal unit's LateInitialize() while loading the Kilo Mech Recharger room. Trace the non-number value back to its source during atom initialization. Done means this initialization path no longer raises the reported error.

Written by the indexing model from the issue text.