Abstract: Systems and methods for low-manganese welding alloys are disclosed. An example arc welding consumable may comprise: between 0.4 and 1.0 wt % manganese; strengthening agents selected from the group consisting of nickel, cobalt, copper, carbon, molybdenum, chromium, vanadium, silicon, and boron; and grain control agents selected from the group consisting of niobium, tantalum, titanium, zirconium, and boron. The grain control agents may comprise greater than 0.06 wt % and less than 0.6 wt % of the welding consumable. The resulting weld deposit may comprise a tensile strength greater than or equal to 70 ksi, a yield strength greater than or equal to 58 ksi, a ductility (as measured by percent elongation) of at least 22%, and a Charpy V-notch toughness greater than or equal to 20 ft-lbs at ?20° F. The welding consumable may provide a manganese fume generation rate less than 0.01 grams per minute during the arc welding operation.

Abstract: Systems and methods for low-manganese welding alloys are disclosed. An example arc welding consumable may comprise: between 0.4 and 1.0 wt % manganese; strengthening agents selected from the group consisting of nickel, cobalt, copper, carbon, molybdenum, chromium, vanadium, silicon, and boron; and grain control agents selected from the group consisting of niobium, tantalum, titanium, zirconium, and boron. The grain control agents may comprise greater than 0.06 wt % and less than 0.6 wt % of the welding consumable. The resulting weld deposit may comprise a tensile strength greater than or equal to 70 ksi, a yield strength greater than or equal to 58 ksi, a ductility (as measured by percent elongation) of at least 22%, and a Charpy V-notch toughness greater than or equal to 20 ft-lbs at ?20° F. The welding consumable may provide a manganese fume generation rate less than 0.01 grams per minute during the arc welding operation.

Abstract: Robot charging dock includes a charge connector configured to mate with a charging port of a mobile robot. There is a charge connector frame having a front surface on which the charge connector is mounted. The front surface has a first side edge and a second side edge. There is a front cover disposed over the charge connector frame which has an aperture through which the charge connector protrudes. At least a portion of the front cover is spaced from the front surface of the charge connector frame, defining an internal region. There is an opening to the internal region formed along at least a portion of a perimeter of the aperture and there is a light source disposed in the internal region. The light source is directed toward the opening to allow the light source to illuminate charge connector.

Abstract: A mobile robot having a removable wheel-drive assembly, comprising a mobile base having a chassis and a first wheel well member with a flange. There is a removable wheel drive assembly with a mounting bracket. There is a motor drive unit disposed on the mounting bracket and a wheel/tire connected to the motor drive unit via an axle. There is a second wheel well member on the mounting bracket and positioned between the motor drive unit and the wheel. The second wheel well member includes a central section having an aperture through which the axle passes and a top surface. The top surface of the central section of the second wheel well member engages with the flange of the first wheel well member of the mobile base.

Abstract: A data storage system includes a first storage layer, a second storage layer, an I/O manager, and a data organizer. The first storage layer utilizes a first type of data storage device. The first storage layer includes (i) a first data bucket that includes first data having a first data attribute, the first data bucket including a first data limit, and (ii) a second data bucket. The second storage layer utilizes a second type of data storage device. The I/O manager receives a data write request from the user and directs the data write request to the first storage layer. The data organizer (a) determines whether data in the data write request has the first data attribute; and (b) stores the data in the data write request in at least one of the first data bucket and the second data bucket if the data in the data write request has the first data attribute.

Abstract: Systems and methods for mapping random data writes to sequential or semi-sequential storage. Data writes may be initially directed to an SSD or other relatively low latency and high IOPS data storage layer. The data may remain in the SSD storage layer until a group of data may be written, together, to a sequential or semi-sequential storage layer. A data organizer may group the data into data buckets based on tags and/or policies associated with the data. In this way, data subject to similar lifetime, priority, data protection, and/or other policies may be stored on a same segment or other portion of the sequential storage layer. Similarly, data having similar access patterns, authors, files, objects, or project affiliations, may be stored together on a same segment of the sequential storage layer.

Abstract: Systems and methods for data management using tagging rules and/or policies. The systems and methods described herein may allow users or administrators to easily label data, so as to organize the data in using any suitable terminology or parameters. Tagging rules (or tag rules) may apply or assign one or more tags to a data file or object. A tag may relate to various components of the data file or object. For example, a tag may relate to a creation date, author, size, or information within the data, such as whether the file or object includes a picture. Once the data is associated with one or more tags, policies may determine how the data is manipulated, stored, accessed, or otherwise used. Policies may relate to actions or operations to be performed with respect to data having one or more particular tags.

Abstract: Systems and methods for data management using tagging rules and/or policies. The systems and methods described herein may allow users or administrators to easily label data, so as to organize the data in using any suitable terminology or parameters. Tagging rules (or tag rules) may apply or assign one or more tags to a data file or object. A tag may relate to various components of the data file or object. For example, a tag may relate to a creation date, author, size, or information within the data, such as whether the file or object includes a picture. Once the data is associated with one or more tags, policies may determine how the data is manipulated, stored, accessed, or otherwise used. Policies may relate to actions or operations to be performed with respect to data having one or more particular tags.

Abstract: Systems and methods for mapping random data writes to sequential or semi-sequential storage. Data writes may be initially directed to an SSD or other relatively low latency and high IOPS data storage layer. The data may remain in the SSD storage layer until a group of data may be written, together, to a sequential or semi-sequential storage layer. A data organizer may group the data into data buckets based on tags and/or policies associated with the data. In this way, data subject to similar lifetime, priority, data protection, and/or other policies may be stored on a same segment or other portion of the sequential storage layer. Similarly, data having similar access patterns, authors, files, objects, or project affiliations, may be stored together on a same segment of the sequential storage layer.

Abstract: Systems and methods for data management using tagging rules and/or policies. The systems and methods described herein may allow users or administrators to easily label data, so as to organize the data in using any suitable terminology or parameters. Tagging rules (or tag rules) may apply or assign one or more tags to a data file or object. A tag may relate to various components of the data file or object. For example, a tag may relate to a creation date, author, size, or information within the data, such as whether the file or object includes a picture. Once the data is associated with one or more tags, policies may determine how the data is manipulated, stored, accessed, or otherwise used. Policies may relate to actions or operations to be performed with respect to data having one or more particular tags.

Abstract: Systems and methods for mapping random data writes to sequential or semi-sequential storage. Data writes may be initially directed to an SSD or other relatively low latency and high IOPS data storage layer. The data may remain in the SSD storage layer until a group of data may be written, together, to a sequential or semi-sequential storage layer. A data organizer may group the data into data buckets based on tags and/or policies associated with the data. In this way, data subject to similar lifetime, priority, data protection, and/or other policies may be stored on a same segment or other portion of the sequential storage layer. Similarly, data having similar access patterns, authors, files, objects, or project affiliations, may be stored together on a same segment of the sequential storage layer.