Trials Frontier Data Cubes
Trials Frontier hack hints guides reviews promo codes easter eggs and more for android application. Trials Frontier cheats tips and tricks added by pro players, testers and other users like you. Ask a question or add answers, watch video tutorials & submit own opinion about this game/app.
In computer programming contexts, a data cube (or datacube) is a multi-dimensional ('n-D') array of values. Typically, the term datacube is applied in contexts where these arrays are massively larger than the hosting computer's main memory; examples include multi-terabyte/petabyte data warehouses and time series of image data.
The data cube is used to represent data (sometimes called facts) along some measure of interest.For example, in OLAP such measures could be the subsidiaries a company has, the products the company offers, and time; in this setup, a fact would be a sales event where a particular product has been sold in a particular subsidiary at a particular time. In satellite image timeseries measures would be Latitude and Longitude coordinates and time; a fact would be a pixel at a given space/time coordinate as taken by the satellite (following some processing that is not of concern here).Even though it is called a cube (and the examples provided above happen to be 3-dimensional for brevity), a data cube generally is a multi-dimensional concept which can be 1-dimensional, 2-dimensional, 3-dimensional, or higher-dimensional.In any case, every dimension represents a separate measure whereas the cells in the cube represent the facts of interest. Sometimes cubes hold only few values with the rest being empty, i.e.: undefined, sometimes most or all cube coordinates hold a cell value. In the first case such data are called sparse, in the second case they are called dense, although there is no hard delineation between both.
History[edit]
Multi-dimensional arrays have long been familiar in programming languages. Fortran offers 1-D arrays and arrays of arrays, which allows the construction higher-dimensional arrays. APL supports n-D arrays with a rich set of operations. All these have in common that arrays must fit into main memory and are available only while the particular program maintaining them (such as image processing software) is running.
A series of data exchange formats support storage and transmission of datacube-like data, often tailored towards particular application domains. Examples include MDX for statistical (in particular, business) data, Hierarchical Data Format for general scientific data, and TIFF for imagery.
In 1992, Peter Baumann introduced management of massive datacubes with high-level user functionality combined with an efficient software architecture.[1] Datacube operations include subset extraction, processing, fusion, and in general queries in the spirit of data manipulation languages like SQL.
Some years after, the datacube concept was applied to describe time-varying business data as datacubes by Jim Gray, et al,[2] and by Venky Harinarayan, Anand Rajaraman and Jeff Ullman[3] which rank among the top 500 most cited computer science articles over a 25 year period.[4]
10 second ninja x gamemaker edition 1. Around that time, a working group on Multi-Dimensional Databases ('Arbeitskreis Multi-Dimensionale Datenbanken') was established at German Gesellschaft für Informatik.[5][6]
Datacube Inc. was an image processing company selling hardware and software applications for the PC market in 1996, however without addressing datacubes as such.
The EarthServer initiative has established geo data cube service requirements.[7]
Standardization[edit]
In 2018, the ISOSQL database language was extended with datacube functionality as 'SQL -- Part 15: Multi-dimensional arrays (SQL/MDA)'.[8]
Web Coverage Processing Service is a geo datacube analytics language issued by the Open Geospatial Consortium in 2008. In addition to the common data cube operations, the language knows about the semantics of space and time and supports both regular and irregular grid datacubes, based on the concept of coverage data.
An industry standard for querying business datacubes, originally developed by Microsoft, is MultiDimensional eXpressions.
Implementation[edit]
Many high-level computer languages treat data cubes and other large arrays as single entities distinct from their contents.These languages, of which APL, IDL, NumPy, PDL, and S-Lang are examples, allow the programmer to manipulate complete film clips and other data en masse with simple expressions derived from linear algebra and vector mathematics. Some languages (such as PDL) distinguish between a list of images and a data cube, while many (such as IDL) do not.
Array DBMSs (Database Management Systems) offer a data model which generically supports definition, management, retrieval, and manipulation of n-dimensional datacubes. This database category has been pioneered by the rasdaman system since 1994.[9]
Applications[edit]
Multi-dimensional arrays can meaningfully represent spatio-temporal sensor, image, and simulation data, but also statistics data where the semantics of dimensions is not necessarily of spatial or temporal nature. Generally, any kind of axis can be combined with any other into a datacube.
Mathematics[edit]
In mathematics, a one-dimensional array corresponds to a vector, a two-dimensional array resembles a matrix; more generally, a tensor may be represented as an n-dimensional data cube.
Science and engineering[edit]
For a time sequence of color images, the array is generally four-dimensional, with the dimensions representing image X and Y coordinates, time, and RGB (or other color space) color plane. For example, the EarthServer initiative[10] unites data centers from different continents offering 3-D x/y/t satellite image timeseries and 4-D x/y/z/t weather data for retrieval and server-side processing through the Open Geospatial ConsortiumWCPS geo datacube query language standard.
A data cube is also used in the field of imaging spectroscopy, since a spectrally-resolved image is represented as a three-dimensional volume.
Business intelligence[edit]
In online analytical processing (OLAP), data cubes are a common arrangement of business data suitable for analysis from different perspectives through operations like slicing, dicing, pivoting, and aggregation.
See also[edit]
References[edit]
- ^Baumann, Peter (April 1992). 'Language Support for Raster Image Manipulation in Databases'. Graphics Modeling and Visualization in Science and Technology. Int. Workshop on Graphics Modeling, Visualization in Science & Technology. Darmstadt, Germany: Springer (published 1993). pp. 236–245. doi:10.1007/978-3-642-77811-7_19.
- ^Gray, Jim; Chaudhuri, Surajit; Bosworth, Adam; Layman, Andrew; Reichart, Don; Venkatrao, Murali; Pellow, Frank; Pirahesh, Hamid (January 1997). 'Data Cube: A Relational Aggregation Operator Generalizing Group-By, Cross-Tab, and Sub-Totals'. Data Mining and Knowledge Discovery. 1 (1): 29–53. doi:10.1023/A:1009726021843.
- ^Harinarayan, Venky; Rajaraman, Anand; Ullman, Jeffrey D. (1996). 'Implementing data cubes efficiently'. Implementing Data Cubes Efficiently. pp. 205–216. CiteSeerX10.1.1.41.1205. doi:10.1145/233269.233333. ISBN978-0897917940.
- ^500 Most Cited Computer Science Articles (501–600), CiteSeer. 12 June 2009. Retrieved 21 March 2017.
- ^Der GI-Arbeitskreis Multidimensionale Datenbanken stellt sich vor, Peter Baumann, Wolfgang Lehner, 1997, Datenbank Rundbrief Volume 19, 1997, http://dblp.uni-trier.de/db/journals/gidr/gidr19.html#BaumannL97
- ^Rückblick auf den GI-Arbeitskreis Multidimensionale Datenbanken, Peter Baumann, 1999, Datenbank Rundbrief Volume 23:, 1999, http://dblp.uni-trier.de/db/journals/gidr/gidr23.html#Baumann99
- ^'The Database Manifesto'. www.earthserver.eu. Retrieved 2017-09-21.
- ^'ISO/IEC DIS 9075-15 Information technology -- Database languages -- SQL -- Part 15: Multi-dimensional arrays (SQL/MDA)'. Retrieved 2018-05-27.
- ^'Management of Multidimensional Discrete Data'(PDF). www.vldb.org. Retrieved 2017-09-21.
- ^'EarthServer - Big Datacube Analytics at Your Fingertips'. www.earthserver.eu. Retrieved 2017-03-31.
IntroductionSoft robotic locomotion is of interest due to the ability of compliant systems to deal with uncertain terrain. These techniques are typically inspired by biological organisms, such as caterpillars, snakes and insects. There are a range of different materials and soft actuators that can be used for the fabrication of such devices, such as elastomers , shape memory alloys (SMAs) , dielectric elastomers , and kirigami skins.Of these materials, elastomers are a popular choice as they are highly versatile and compliant whilst being light-weight. For these reasons, they have been used in a variety of locomoting soft robots. One such soft robot designed by and demonstrates a crawling motion.
The soft robot is completely manufactured with the elastomer silicone and uses this material to create a frictional difference with the ground between the leading and tail end of the robot that alternates as it moves to favor forward motion. However, the frictional contact between the elastomer and the ground leads to a high rate of wear, in turn causing a risk of puncture. This limitation can also be seen in the robot that uses vibrations to bounce across a surface on its elastomer bellows. The walking legged robots by utilize elastomers to create joints to move more rigid components or legs. These are potentially better suited to traversing uneven terrains than crawling robots, not only as the soft elastomer is less likely to get damaged as it is not in contact with the surface, but also because they have a smaller surface area in contact with the ground, resulting in less energy being used to overcome friction and allowing them to navigate over obstacles.Rolling has the potential to be a faster method of locomotion for soft robots, however it comes at a cost of increased unpredictable path following and complex simulation and control. Different technologies have been used to achieve the rolling motion.
Created a soft robot with patterns of dielectric elastomers (DEAs) in the shape of a ring. Activating these DEAs results in extension of those regions and therefore deformation of the ring.
Other methods of rolling have been achieved with pressurizing fabric tubes which have been constrained in certain directions to generate bending. Successful application of elastomers for the use of rolling locomotion has been demonstrated by and which uses a technique known as particle jamming. Silicone elastomer filled with particles and arranged in a sphere can be vacuumed to change its stiffness. Rolling is achieved when specific elastomer cells are unjammed causing them to reduce in stiffness. A central actuator then causes expansion of these cells and a change of shape of the sphere. Although a completely soft locomoting robot is achieved, the thickness of the elastomer and number of elastomer cells will limit the complete morphing ability of the robot.Applications of soft robotics for locomotion are expansive and have overcome some of the challenges faced by rigid robots. However, their pliable nature comes with the challenge of control due to their high number of degrees of freedom.
The non-linearities within the actuation of soft robots can result in systems that are difficult to predict and the repeatability of motion can be challenging. As such, control schemes for soft robotic systems often require intrinsic and extrinsic sensing and/or localization, alongside complex control systems for locomotion. Additionally, current systems generally lack the stability of conventional robotic systems and resting positions can vary from step to step. Soft robotic systems often also require tethering to off-board pneumatic and electronic components, resulting in long tethers that limit the robot's range of motion and reach.We present RUBIC, the Rolling, Untethered, Ballooning, Intelligent Cube. The external structure, actuation mechanisms and internal structure are shown in. RUBIC utilizes fluidic elastomer actuators to locomote from face to face, as shown in. In contrast to past soft robotic systems, RUBIC can approximately follow a discrete, predictable path along a grid.
In addition, RUBIC is operable untethered as all electronics are on-board and commands are received via remote control. In this paper we describe the design of RUBIC, with focus on the characterization of the actuators and quantification of locomoting patterns. Robot DesignThe fundamental concept of RUBIC is a cube that locomotes by rolling. Actuation is provided by 24 fluidic elastomer actuators, attached to the faces of the cube, that inflate to create a rolling motion, as shown in.
To achieve locomotion in two dimensions, each face comprises four actuators in a 2 by 2 matrix. When two adjacent actuators on the bottom face of the cube inflate, they lift that side of the cube causing it to roll onto the adjacent face. Repeating this process allows RUBIC to navigate through its environment along a discretised path. The cubic structure ensures that the robot can be directed left, right, forwards or backwards with a simple control system.
The fall of jake paul lyrics. And the same cars, tooIt's really not that hardOh hey, by the way, welcome to the top little brotherFeels good, huh?But let's not forget how you got hereYah, yeetLittle brother Jakey try to roast me?
Power is provided via an on-board lithium polymer battery, allowing for approximately an hour of locomotion per charge. Control signals are sent via Bluetooth, allowing the robot to operate untethered.A cube was selected as the base structure for the robot based on the outcome of analysis into the dynamics of platonic solids with equal volume. The five platonic solids were considered: tetrahedron, cube, octahedron, dodecahedron and icosahedron. These solids were then analyzed based on three factors: rotation angle; actuator volume and energy.
For rotation angle α, we calculated the angle each solid must be rotated from its stationary position in order to roll to the next face, e.g., 45° for a cube. Though icosahedron have the lowest values in all three metrics, there are other factors to consider. Fabrication complexity increases with the number of faces, as each face requires between 3 and 5 actuators, depending on the solid. Thus, cubes and octahedrons would require 24 actuators to enable multi-directional locomotion and dodecahedrons and icosahedrons would require 60. Another consideration is in the solid's stability when at rest, as it is anticipated that the resultant robot would be used in unstable environments. In this instance, a higher rotation angle is beneficial, as it means that the solid is less likely to roll due to environmental perturbations. As such, cubes were selected based on the low actuator volume required to reach the rotation angle compared with tetrahedrons and their stability compared with solids with more faces.
Additionally, cubes are the only platonic solid capable of straight line locomotion, as all other solids follow angular paths when rolled from face to face. Robot Fabrication 2.1.1. Internal StructureThe internal structure of RUBIC can be seen in. We designed the layout to allow for an even distribution of weight, thereby minimizing the interference with the kinematics of the cube. The components are fixed to 4 layers of laser cut plywood as shown in. The outer two layers house 12 3-way solenoid valves (5-6 V; Zonhen Electric Appliances), 6 on the top layer and 6 on the base layer. The middle two layers contain the PCB, the Lithium-ion Polymer battery (7.4 V; 1000 mAh, Turnigy) and 2 pumps (3 V, KPM14A; Koge Electronics CO., LTD.).
Both pumps are connected to all 12 valves to ensure maximum pneumatic power, and each valve is connected to two actuators on opposite sides of the cube, as shown in,. A key challenge in our design of RUBIC was to minimize size and weight in order to reduce the load on the pumps and increase locomotion speed. Size was a particular issue as actuating a larger cube would require a greater torque and create a greater distance for the actuators to lift in order to locomote. As a compromise, we chose to use 12 valves connected to opposing pairs of actuators, rather than having 24 valves with one valve per actuator. This saved on space and weight, allowing RUBIC to be a 10 cm cube and 0.83 kg, while containing all of the required electronics. However, this resulted in a decrease in speed since the pumps were then required to pump twice as many actuators at a time. It is also the cause of RUBIC's unique appearance when locomoting, observable in.
ActuatorsWe manufactured the pneumatic actuators from silicone elastomer (Ecoflex 00-30 TM; Smooth-On), as it is light-weight, versatile and highly compliant, reaching up to 900% expansion before tearing. Further characterization of the elastomer has been performed. Actuators were manufactured in a 2-step molding process. Bases and covers were fabricated separately, before being cured together along their edges to create a sealed air chamber, as shown in. Each actuator measures 50 × 50 × 8 mm.
The wall and ceiling thicknesses of each actuator are approximately 2 mm and 1.5 mm respectively. The base of the actuators are 3 mm thick and contain a constraining paper layer to limit expansion at the base. We designed the actuators with four right angled silicone extrusions to ease connection with the internal Medium-Density Fiberboard (MDF) body. A ring of silicone was also extruded from the center of the actuator to interface with the pneumatic input (external and internal diameters of 8 mm and 4 mm, respectively). Extruded structures are 4 mm in length, long enough to extend through holes in the 3 mm MDF body.
Actuators were fixed to the internal structure of the cube with the use of silicone adhesive (Sil-Poxy TM; Smooth-On). We dyed the actuators a different color for each side of the cube to make them distinguishable and to simplify setting up the control mechanism. Principle of OperationAt start up, the Bluetooth communication channel is enabled (visual feedback is provided by an LED to confirm connection) and all valves and pumps are off. We control the robot from a PC or tablet via a graphical user interface (GUI) that was developed for ease of operation, as shown in.
The GUI includes switches to initialize pumps and manipulate which valves are open or closed at any time. We update valves by selecting the actuator on each image that needs to be opened and then click “Update Valves,” thus updating all valves at once. Opening a single valve translates to activating two actuators on the robot, as described in section 2.1.1 and illustrated in. We operate the robot by observing which side faces the ground, finding the corresponding colored face within the GUI and opening the two valves opposite to the direction of travel. The GUI updates all valves simultaneously, overcoming potential problems with off-setting actuation, which would result in an unwanted tilt.We designed RUBIC to discretise the operable space surrounding it. This is a novelty that can be difficult to accomplish with soft robotic components, due to non-linearity of actuation and the high number of degrees of freedom that soft materials exhibit. In principle, this means that RUBIC translates its environment into a grid structure along which it locomotes.
Inflating two actuators opposite to the direction of travel results in locomotion to the next grid point, either to the left, right, front or back. This discretisation allows for predictions to be made about how RUBIC can move in space. It also allows environments to be mapped such that routes can be planned prior to actuation of the robot. Actuator CharacterizationThe fluidic elastomer actuators are the fundamental components that allow locomotion of this robot. In this section we detail the steps taken to characterize these actuators.
MethodWe designed RUBIC to operate untethered, thus increasing its operation space and eradicating restrictions resultant from a tethered connection. In order to operate untethered, all of the components had to be integrated inside the body of the robot. To save space, smaller pumps had to be used and the number of valves reduced, as shown in and discussed in section 2.1.1.
Consequently, the pumps inflate two actuators simultaneously. To investigate the performance impact of this set-up we tested the actuators in terms of their vertical displacement and pressure reached with time for actuation of single and double (paired) actuators.
We conducted tests with pumps equivalent to the on board pumps installed in RUBIC. Testing in this way allowed for a comparison in terms of both speed and pressure dynamics.We attached the actuators to the bottom and, in the double actuator test, to the top of a linear guide. To test the performance of a single base actuator in lifting the robot, we set the weight of the supporting structure to match half of the robot's weight, as we assumed that one actuator provides half of the lift required for locomotion.
We inflated the actuators until a height of 75 mm was reached, as this was the approximate height required to roll onto the next face, described in section 4.1. We maintained this level until a valve (S070C-SBG-32; BEST Pneumatics Inc.) was opened to deflate the actuators.
We measured the height with a laser displacement meter (LK-G152; Keyence) and the pressure inside the actuators with a pressure gauge (HSCDANN030PGAA5; Honeywell). The results we obtained allow for comparison between the single (unpaired) and double (paired) actuators. ResultsIn, from time 0 to t 1, the pump is switched on to activate inflation of the actuators. From t 1 to t 2, the pump is switched off but the air is maintained in the system (i.e., the actuators are kept inflated); after time t 2 the valve is opened to release the air and allow the actuators to deflate. Shows the height and pressure measurements for actuation of the paired actuators, closely representing the actuation scheme used in RUBIC. For each pair of actuators, only the actuator on the bottom face of RUBIC is load-bearing and responsible for lifting the robot. To replicate this in the paired actuator experiment, we applied a load to one actuator and allowed the other to actuate freely.
During the initial inflation period, the rate of vertical displacement drops temporarily (between A1 and A2) because the inflation of the top actuator is greater than that of the bottom actuator. As the pressure remains constant, this behavior can be explained by the slight difference in material thickness of the actuators and the additional external load acting on the bottom actuator (i.e., the weight of the test rig). While maintaining constant height, the actuator rapidly snapped through to a stable, high-strain ballooned state. This dynamic snap-through is a well studied phenomena with inflated hyperelastic membranes. Toward the end of the deflation period (A6), the rate of pressure and height change levels due to a fold that developed in the bottom actuator.
In that period, the top actuator deflated at a higher rate before both actuators returned to their initial configuration (A7).The same general behavior can be observed using only one actuator. However, the actuator inflates at a steadier rate (B1 and B2 in ) as no mutual interference between the two actuators occurs. It also takes approximately half the time to reach the desired height. Considering the same general behavior for the two tested actuator configurations, the use of double actuator inflation is a valid trade-off to enable an untethered robot, although at the cost of locomotion speed. Locomotion CharacterizationLocomotion of RUBIC is achieved by rolling from one face onto the next in a quantized Cartesian space. In this section, we describe the steps taken to characterize the locomotion abilities of RUBIC.
Analysis of Locomotion Schemes 4.1.1. MethodLocomotion of RUBIC consists of opening pairs of valves, allowing time for the actuators to fill with air and waiting for a tipping point to be passed (the moment at which the center of mass of the robot passes over the point of contact with the ground). A single step of the robot can be modeled simply by considering the leading edge of RUBIC as a hinge and then calculating the diameter the actuator has to inflate to (inflated diameter) in order to reach the tipping point, as depicted in. Assuming uniform weight distribution within the robot, we deduce that the angle required for the robot to reach its tipping point is 45° when the robot locomotes with rear actuators alone. We propose that a second locomotion pattern could reduce the time required to complete a single step. This second pattern consists of activating the rear actuators as before, but then activating the front actuators during the roll to assist the motion. Diagram of height required from actuators to reach tipping angle of RUBIC for two actuation schemes: (A) Rear actuators only; θ A = 45°, resulting in actuator height h A = 3Lsinθ A/4 = 53.03 mm for L = 100 mm.
(B) Front and rear actuators; (B1) rear actuators initially activated until RUBIC reaches minimum angle θ B 1 = t a n - 1 ( 1 / 2 ) = 26. 6°, where the center of mass shifts beyond the center of the front actuators ( L/4 from hinge point), h B1 = 33.58 mm for L = 100 mm, (B2) front actuators are then additionally activated until tipping angle θ B2 = 45° is reached, (where h B2 = h A). Illustrates a theoretical model for this actuation pattern, again assuming uniform weight distribution.
For the front actuators to assist, not impede, the roll, they must be activated once the center of mass has passed over the center of the front actuator. In doing so they provide additional torque about the hinge point. Activation prior to this point does not assist with locomotion, where the angle θ at which the front actuators should be activated was calculated from the geometry of a cube to be at least 26.6° as shown in.To test this alternative actuation pattern, we placed RUBIC in front of a blackout curtain with space to locomote forwards. We cut several freestanding plywood triangles to act as physical representations for each value of angle θ being tested and placed these in front of RUBIC. We then inflated the rear actuators until the base of RUBIC matched the freestanding representation of θ, at which point we inflated the front actuators as shown in. We performed three tests for θ = 10°, 15°, 20°, and 25°. We then extracted time-stamped data, including the point at which valves are opened, the point at which the front actuators are actuated and the end of the roll, from recorded video and used this data to evaluate the effect of changing angle θ.
To determine the linearity of RUBIC's locomotion, we measured the angle of deviation from a straight line path. A primary novelty for RUBIC is the quantization of its environment and its movement within a 2D grid. In order for this pattern of locomotion to be achievable and predictable, the path that RUBIC follows when rolling in any one direction must be as straight as possible.We aligned the robot to a straight line on a large, flat surface and recorded its starting position. RUBIC then locomoted step by step along this line until two full rotations were complete (resulting in a total of 8 steps being taken). We then recorded the final position and calculated the angle of deviation.
We ran 5 trials for both the original locomotion pattern (using rear actuators only) and the alternative pattern (using both rear and front actuators, with front actuators activated once RUBIC reached an angle of 15°, based on the results of the previous test). We also recorded position data for each step within two trials of the alternative actuation pattern to illustrate an example linear path. Shows the experimental set-up and an example path for the line-following experiment where lengths A and B equate to the measured distance and deviation of the final position relative to the central line. We calculated the overall deviation angle α as α = arctan( B/ A). To evaluate RUBIC's capabilities over uneven terrain, we devised a test to measure its performance traversing a surface that included steps that ranged from 20 to 40 mm in 5 mm increments.
For each step, we aligned RUBIC such that the robot landed with the center of the robot just off the edge of the step, as shown in. In this way, the rear actuators were not on the step and were able to continue pushing the ground. The front actuators were then actuated once the base of the robot had reached a 15° angle with the step, making contact with the step and assisting the roll. It was expected that RUBIC would not be able to traverse a step greater than 50 mm since the pivot point between RUBIC and the step would be too high to lift the center of mass over. Video was taken of the experiment and the set up can be seen in.
We extracted time data from video recordings as a metric to compare different climbing methodologies. ResultsFor the original locomotion scheme, with only rear actuators activated, the angle required to make a step was calculated to be 45°. In practice, this was successful and one roll was found to take 55.03 s with standard deviation of 1.04 s across 3 trials.The most time efficient control plan for activating the front actuators was at θ = 15°, decreasing the total time taken to roll to 51.70 s.
Activating the front actuators at an angle of 10° failed, resulting in lifting the front side of RUBIC upward instead of assisting the roll. Additionally, it was found that actuation of the front actuators at θ = 15° increased the total step length by 1.10% as listed in. This occurred due to the inflation of the front actuators generating both a turning force in the direction of travel and an upwards force that lifted the leading edge of the cube from the ground. This has the effect of shifting the point of turn beyond the edge of the cube, resulting in an extended step length.
The trajectory of the leading edge in this scenario is shown in. Gives an example trajectory of RUBIC as it traversed along the central line.
As can be seen, the deviation of RUBIC from the central line increases with each roll. The total deviation and distance traveled by RUBIC were measured and the mean results can be seen in.
The results show that the alternative locomotion scheme, while being faster than the original scheme as previously discussed, also results in a smaller deviation of RUBIC from the central line as it travels. Not only this, but the overall distance traveled by RUBIC for the two rotations was 10 mm further than in the rear actuator case.The deviation of RUBIC from the central line was 12.18% of the distance traveled for the original locomotion scheme and 7.92% for the alternative scheme. While the alternative locomotion scheme (front and rear actuators) is faster and more precise than the original locomotion scheme (rear actuators only), the results of this test show that there is uncertainty in the discretised space RUBIC can navigate. The further RUBIC travels, the greater the uncertainty of its final position. Observation of video recordings shows that much of this uncertainty is due to irregularities in the fabrication of the actuators, as actuators will inflate to different sizes at different rates depending on the thickness of the actuator walls.
This will be elaborated on in the discussion.RUBIC was successfully able to climb step sizes of up to 35 mm, but was not capable of climbing a 40 mm step. The failure of RUBIC to navigate the 40 mm step was due to the maximum expansion of the actuators. However, completion of a 35 mm step is over a third of RUBIC's height and future iterations of RUBIC can be scaled according to the demands of the environment.
In addition, less dramatic terrains with slopes and bumps, rather than sharp corners and steps, may be less of a challenge for RUBIC. DiscussionIn this paper, we have demonstrated RUBIC's ability to locomote on a flat surface and across uneven terrain.
We have also characterized the fluidic elastomer actuators and provided two differing locomoting patterns for RUBIC.For the alternative locomotion scheme, an angle of 26.6° was calculated to be the optimal angle for actuation of the front actuators as illustrated in. However, in practice, the optimal angle was 15° which reduced the time per roll by 3.33 s. Two reasons are presented for this discrepancy between the theoretical and practical optimal angle. Firstly, when the front actuators are activated there is a short delay while they inflate before they touch the ground and provide active assistance.
During this time, RUBIC continues to rotate and, therefore, the angle at which the front actuators are providing assistance is greater than the angle at which they are initially activated. Secondly, the theory does not take into consideration the added torque of the actuators inflating and pushing against each other.
When the front actuators inflate they are enclosed by RUBIC and the inflated rear actuators, and so inflation generates a force against both. This force against the rear actuators would add to the torque acting to roll RUBIC.Deviation from a straight line path while locomoting was also reduced with the alternative locomotion scheme, as shown in.
The angle of deviation was reduced by 2.51° for two complete rotations (i.e., 8 individual rolls), resulting in a linear deviation of 7.92% of the distance traveled. In addition, the distance traveled was increased with the alternative scheme by 1.10% for two complete rotations. The reason for this being that the turning point is shifted forwards (in the direction of travel) during actuation, as actuating the front actuators raises the leading edge (previously the pivot point) of the robot from the ground as illustrated in.We initially proposed the alternative locomotion scheme to improve RUBIC's locomotion speed. Though testing shows that only 3.33 s are saved per roll, a 6% improvement, the alternative locomotion scheme offers other benefits, such as stair climbing, as well. While discrete movement in space is beneficial for route planning and allowing for prediction of motion, there may be instances when RUBIC becomes stuck, or unable to take a full step in a specific direction and needs to locomote away from its grid path.
An instance of this could be if RUBIC is moving within a narrow corridor and its movement grid is misaligned, such that operating in a straight line would result in hitting either wall. In this instance, it would be beneficial to be able to realign RUBIC's locomotion grid, such that RUBIC can then navigate the corridor. Alternating between the alternative locomotion scheme and the original locomotion scheme provides one such method for realigning RUBIC's grid space, as each locomotion scheme has a different step length. This means that small adjustments can be made to RUBIC's locomotion to allow for such difficulties.One of the major drawbacks in this iteration of RUBIC is the pairing of actuators. Due to the coupling of actuators to a single valve, if the power of the pumps is insufficient, the top, unloaded actuators inflate first until they reach the back pressure of the pumps (i.e., when the pressure in the actuator is equal to the pressure from the pumps) only after which the bottom loaded actuators will start to be inflated. The redundant actuation of the top actuators slows the speed down. Actuating a single actuator at a time, rather than two simultaneously as seen in RUBIC, significantly reduced inflation times and would, therefore, increase locomotion speed.
However, due to limited internal space, a larger pump or more valves (to allow one valve per actuator) was not practical in this iteration of RUBIC. Future work will address this issue.The biggest factor that limits the accuracy of the robot is irregularities in the fabrication of the actuators. Slight deviations in actuator wall thickness result in differences in inflation rate and maximum inflation diameter. As a consequence, the actuators rolling RUBIC are slightly imbalanced causing a tilt that sends RUBIC slightly off course as it rolls.
This will be improved in future by refining the actuator fabrication method, ensuring precision and consistency. As a result, this deviation will be minimized and uncertainty in path following reduced.Scalability of RUBIC is of interest for its suitability in applications that may require a smaller robot to navigate intricate environments, or a larger robot to overcome obstacles in a specific terrain. From the calculations approximating the actuator volume required for locomotion (see section 2 or ), we can calculate the actuator volume required for different length scales of RUBIC. This approximation gives a cubic increase in volume for a linear increase in side length. Therefore, doubling the side length of RUBIC to 0.2 m results in an 8-fold increase in actuator volume required to locomote and tripling side length to 0.3 m corresponds to a 27-fold increase in actuator volume required. If we assume a constant flow rate to the actuators this results in a cubic increase in time taken to actuate, significantly reducing locomotion speed. To increase the size of RUBIC, higher capacity pumps would be necessary to maintain performance.
Reducing the size of RUBIC does not have this problem, but requires smaller valves, pumps and electronics to physically fit into the structure. These factors are limitations to the scalability of RUBIC.In this paper, we demonstrate RUBIC, a robot with soft actuators that locomotes by rolling. The novelty of RUBIC compared with other rolling robots, such as, is that its path can be predicted, as it moves along a quantized Cartesian grid. To simplify the control mechanism, future iterations of the robot will include an Inertial Measurement Unit (IMU) so that the robot can self-sense which face is to the ground.
The GUI would then indicate which face should be actuated, allowing for operation of the robot without line of sight and, ultimately, fully autonomous operation. Although many improvements can still be ma.