Numerous scientific studies contributed to continuous improvements of DOCs for oxidizing NO, hydrocarbons (HCs) and CO, and today DOCs are an integral part of almost every emission control system for lean-operated internal combustion engines. In this context, two of the most commonly used materials in exhaust gas catalysis are platinum and palladium, which are particularly exploited for diesel oxidation catalysts (DOCs). Understanding the degradation mechanisms that result in catalyst deactivation is a crucial step towards an increase of catalyst durability, which ultimately allows for saving expensive noble metals. Although decades of intense research efforts resulted in the development of catalytic converters with a high initial activity, catalyst deactivation due to poisoning and hydrothermal aging still poses a challenge. Tightening environmental legislation and more stringent emission standards continuously increase the demand for highly active and durable exhaust gas after-treatment systems. Our study shines a light on the aging behavior of noble metal catalysts under industrially relevant conditions and particularly underscores the highly complex transformation of bimetallic Pt-Pd diesel oxidation catalysts during hydrothermal treatment. Most importantly, we observed pronounced morphological changes for the bimetallic catalyst sample: hydrothermal aging at 750 ☌ causes a stepwise transformation of the Pt-Pd alloy via core-shell structures into inhomogeneous agglomerates of palladium and platinum. While the initial aging step caused the most pronounced deactivation and sintering due to Ostwald ripening, the deactivation rates decline during further aging and the catalyst stabilizes at a low level of activity. Aging induces significant particle sintering that results in a decline of the catalytic activity for all catalyst formulations. Defined in engine/src/Core/Container.By combining scanning transmission electron microscopy, CO chemisorption, and energy dispersive X-ray spectroscopy with CO and NO oxidation light-off measurements we investigated deactivation phenomena of Pt/Al 2O 3, Pd/Al 2O 3, and Pt-Pd/Al 2O 3 model diesel oxidation catalysts during stepwise hydrothermal aging.Only if you have a variable set with Container.exportImage | exportImage(callback, type?, quality?)}: Exports an image of the canvas (without the background property if set), type and quality are optional and are the image output type and Container.exportConfiguration | exportConfiguration()}: Exports the current configuration in JSON, returns a Container.start | start()}: Starts the container, it's different from play | play()}, this will reload Container.stop | stop()}: Stops the container, it's different from pause | pause()}, this will clean up what need to be Container.refresh | refresh()}: Restarts the container, just a stop | start | start()} Container.loadTheme | loadTheme(name)}: Sets the specified theme reloading options, if name is undefined the default theme will be used (if set) ay | play()}: Used to resume the animations, can be stopped using pause | Container.pause | pause()}: Used to pause the animations, can be restarted using play | stroy | destroy()}: Prepare the instance to destruction, you won't retrieve this instance anymore. A refresh | refresh()} after the change is the best thing to Container.sourceOptions}: The options used when the Container} was created, these options will be used only in the Container.particles}: The particles manager, you can add/remove particles from here. Changing this options while playing can result in an unexpected behavior. It's set by Engine.load | tsParticles.load()} and Engine.loadJSON | Container.options}: Where to find the current options loaded.

Container.id}: the Container} id, normally is the related DOM element Container.id} attribute. Otherwise you can retrieve any loaded instance using Engine.dom | tsParticles.dom()} or Engine.domItem | tsParticles.domItem(index)}.

If you get the result of Engine.load | tsParticles.load} the result it's this class, in the Engine.loadJSON | tsParticles.loadJSON} is the then parameter. The Container} class is the manager of the entire tsParticles instance.

Docs2 particles