Anonymous ID: 394d77 Nov. 25, 2020, 9:29 p.m. No.11791632   ๐Ÿ—„๏ธ.is ๐Ÿ”—kun

>>11791558

 

 

The Mesh-Oriented datABase (MOAB)

 

MOAB is a component for representing and evaluating mesh data. MOAB can store structured and unstructured mesh, consisting of elements in the finite element โ€œzooโ€, along with polygons and polyhedra. The functional interface to MOAB is simple, consisting of only four fundamental data types. This data is quite powerful, allowing the representation of most types of metadata commonly found on the mesh. MOAB is optimized for efficiency in space and time, based on access to mesh in chunks rather than through individual entities, while also versatile enough to support individual entity access.

 

The MOAB data model consists of the following four fundamental types: mesh interface instance, mesh entities (vertex, edge, tri, etc.), sets, and tags. Entities are addressed through handles rather than pointers, to allow the underlying representation of an entity to change without changing the handle to that entity. Sets are arbitrary groupings of mesh entities and other sets. Sets also support parent/child relationships as a relation distinct from sets containing other sets. The directed-graph provided by set parent/child relationships is useful for modeling topological relations from a geometric model and other metadata. Tags are named data which can be assigned to the mesh as a whole, individual entities, or sets. Tags are a mechanism for attaching data to individual entities and sets are a mechanism for describing relations between entities; the combination of these two mechanisms is a powerful yet simple interface for representing metadata or application-specific data. For example, sets and tags can be used together to describe geometric topology, boundary condition, and inter-processor interface groupings in a mesh.

 

MOAB's API is documented in the moab::Interface class. Questions and comments should be sent to moab-dev at mcs.anl.gov.

 

User's Guide (MOAB 4.6)

 

Developer's Guide (MOAB 4.6)

 

I/O and Meta-Data Storage Conventions in MOAB

 

https://www.mcs.anl.gov/~fathom/moab-docs/html/index.html

Anonymous ID: 394d77 Nov. 25, 2020, 9:40 p.m. No.11791796   ๐Ÿ—„๏ธ.is ๐Ÿ”—kun   >>1843

>>11791658

[C]H(i)[C]agO

 

MCS Menu

 

MCS Division

About MCS

 

Research

 

News

Events

Publications

 

Share

 

 

 

 

 

 

 

A leader in the computing sciences, the MCS Division provides the numerical tools and technology for solving some of our nationโ€™s most critical scientific problems.

 

In addition to our world-class research, we develop the software for some of the fastest, most powerful computer systems in the world: systems that are enabling scientists to tackle problems previously considered infeasible.

Anonymous ID: 394d77 Nov. 25, 2020, 10:06 p.m. No.11792096   ๐Ÿ—„๏ธ.is ๐Ÿ”—kun

>>11791962

>Watch the Water(marks)

 

"

The watermark is invisible under visible light (left), but not when exposed to UV light (right)

EPFL

"

 

 

Using a machine ordinarily used for manufacturing LEDs, a proprietary blend of chemicals is applied to a glass surface as a vapor, forming into photonic crystals. These crystals are in turn made up of ultrathin layers of atoms, and they convert UV light into colors โ€“ different colors can be produced by tweaking the geometry and alignment of the crystals on the glass.

 

Lithographic printing techniques are used to mask some areas of the surface, so that the watermark takes on a watch-specific pattern. When viewed under visible light, that pattern is invisible to the human eye, in no way altering the watch's appearance. Under UV light, however, the watermark shows up.

 

According to EPFL, counterfeiting such a watermark would be as difficult as forging the Swiss 50-franc note. Not only would counterfeiters need to know which chemicals to use and in what proportions, but they would also need expensive equipment to apply them.

 

 

https://newatlas.com/dnawatch-nanoscopic-watermark/44102/