Abstract: An ophthalmic device includes an optic including an optic axis and a closed-loop haptic structure coupled to the optic via a frame surrounding the optic, the closed-loop haptic structure including a closed loop extending from first and second attachment points to the frame. The closed loop includes a first hinge and a second hinge. The first hinge has a first section having a first component extending in a first angular direction, a second section having a second component extending in a second angular direction opposite to the first angular direction, and a first connecting section between the first section and the second section. The second hinge has a third section having a third component extending in the second angular direction, a fourth section having a fourth component extending in the first angular direction, the fourth section being connected to the second section to form the closed loop.

Abstract: A method for monitoring and controlling neutron beams includes performing a calibration process for a monitoring dosimeter at a first set of conditions for directing a neutron beam towards an object location, the neutron beam being emitted from a neutron-generating target in response to an incident charged particle beam, the process comprising: obtaining data indicating a first neutron flux measured by the monitoring dosimeter between the monitoring dosimeter and the object location, the monitoring dosimeter offset from the axis by a distance equal to or greater than the beam radius; obtaining data indicating a second neutron flux measured by a reference dosimeter between the target and the object location; storing calibration data including a correlation between the first neutron flux and the second neutron flux; and based on the calibration data, using the monitoring dosimeter to monitor neutron flux incident on a patient during boron neutron capture therapy treatment.

Abstract: A device establishes a key recovery policy and generates a key that is protected based on the key recovery policy. The key recovery policy indicates which combinations of other entities can recover the protected key. The device generates different shares of the protected key, each share being a value that, in combination with the other share(s), allows the protected key to be recovered. Each share is associated with a particular leaf agent, the device encrypts each share with the public key of the leaf agent associated with the share and provides the encrypted share to a service. When recovery of the protected key is desired, a recovering authority can generate the protected key only if the recovering authority receives decrypted shares from a sufficient one or combination of leaf agents as indicated by the recovery policy.

Abstract: A device establishes a key recovery policy and generates a key that is protected based on the key recovery policy. The key recovery policy indicates which combinations of other entities can recover the protected key. The device generates different shares of the protected key, each share being a value that, in combination with the other share(s), allows the protected key to be recovered. Each share is associated with a particular leaf agent, the device encrypts each share with the public key of the leaf agent associated with the share and provides the encrypted share to a service. When recovery of the protected key is desired, a recovering authority can generate the protected key only if the recovering authority receives decrypted shares from a sufficient one or combination of leaf agents as indicated by the recovery policy.