plesty-pol-pl 0.2.0.dev1__tar.gz

plesty_pol_pl-0.2.0.dev1/.env.example

@@ -0,0 +1,35 @@
+# The values setup.yaml names, and overrides for a run. A bench writes `.env`
+# from these when it installs the module; by hand, copy this file to `.env`.
+# Loaded by plesty.lib.utils.EnvSettings; the process environment overrides `.env`.
+# Measurement tuning does NOT belong here — it lives in config/*.yaml.
+#
+# setup.yaml names the benches and each device's bench (`host_name`). It is
+# committed, so where each bench is, its token and where it sees the shared
+# data disk are set here, in the variables it names. The bench running the
+# experiment serves each device on its bench, which may write anywhere under
+# that bench's view of the disk, and gives the run HWP_ADDRESS and
+# SPEC_ADDRESS; the run is given PLESTY_DATA, this machine's view of the disk,
+# and its runs go to <PLESTY_DATA>/pol-pl.
+
+# Where the machine the experiment runs on (the bench `bench-local`, the one
+# without an address) sees the shared data disk. /tmp for the demo, which runs
+# on this machine alone.
+LOCAL_DATA=/tmp
+
+# A bench on another machine, when setup.yaml names one (see the example
+# there): where its agent listens, the token it checks, and where it sees the
+# same shared disk.
+# BENCH_XXX_HOST=
+# BENCH_XXX_TOKEN=
+# BENCH_XXX_DATA=
+
+# Everything below is an override: without the bench, or to point one device
+# elsewhere for a test, set its ZMQ address directly (the sub-device name
+# upper-cased); a device set here is not served by its bench.
+# HWP_ADDRESS=tcp://localhost:5555
+# SPEC_ADDRESS=tcp://localhost:5556
+
+# This machine's view of the shared data disk, when the bench does not give it.
+# Runs go to <PLESTY_DATA>/pol-pl unless --run-root says otherwise, and their
+# spectra to each run's raw/spec.
+# PLESTY_DATA=

plesty_pol_pl-0.2.0.dev1/.gitignore

@@ -0,0 +1,71 @@
+# Custom
+.deprecated/
+logs/
+runs/
+
+# Field test and check reports. The JSON documents are the published
+# artifacts — hub.plesty.net and manager.plesty.net read them, so they are
+# committed. The markdown and JSONL forms are for whoever ran the test: they
+# carry the host name, the instrument address, its serial and the lab's file
+# paths, and a hub repository is world-readable.
+# An interrupted `plesty init field-test` leaves its answers here.
+.plesty-field-test.partial.json
+
+reports/**/*.md
+reports/**/*.jsonl
+reports/*.md
+reports/*.jsonl
+
+# Auto-generated device reference pages (regenerated by `plesty docs`)
+docs/_generated/
+
+# Python bytecode and caches
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions and shared libraries
+*.so
+*.pyd
+*.dll
+
+# Packaging and build artifacts
+build/
+dist/
+*.egg-info/
+.eggs/
+
+# Local credentials — keep `.env.example` tracked, never the real `.env`
+.env
+
+# Virtual environments
+.venv/
+venv/
+env/
+ENV/
+.uv_cache/
+
+# Test and coverage outputs
+.pytest_cache/
+.coverage
+.coverage.*
+htmlcov/
+.mypy_cache/
+.ruff_cache/
+
+# Jupyter
+.ipynb_checkpoints/
+
+# Logs and runtime files
+*.log
+*.pid
+
+# IDE/editor
+.vscode/
+.idea/
+*.swp
+*.swo
+
+# OS files
+.DS_Store
+Thumbs.db

plesty_pol_pl-0.2.0.dev1/.gitlab-ci.yml

@@ -0,0 +1,16 @@
+stages:
+  - check
+  - security
+  - deploy
+  - release
+
+variables:
+  # Required for versioningit: the runner must fetch full Git history and tags.
+  GIT_DEPTH: "0"
+
+include:
+  - component: $CI_SERVER_FQDN/plesty/plesty-ci/plesty-standard-ci@main
+    inputs:
+      standard: quantum
+      extra_branch: exp
+      access_token: $CI_BOT_TOKEN

plesty_pol_pl-0.2.0.dev1/.mailmap

@@ -0,0 +1 @@
+Yunshuang Yuan <yuanyunshuang@163.com> yys <yuanyunshuang@163.com>

plesty_pol_pl-0.2.0.dev1/CHANGELOG.md

@@ -0,0 +1,139 @@
+# Changelog
+
+The format is based on [Keep a Changelog](https://keepachangelog.com).
+
+## [Unreleased]
+
+## [0.2.0] - 2026-10-27
+
+Opens the 0.2 line, on the released plesty-lib 0.6.0; 0.1 stays supported as
+the maintenance line. The demo's devices are pinned, so the Bench app's welcome
+can install this release and run the same demo for as long as it is installed.
+
+### Changed
+- **Spectra are recorded where the spectrometer's bench writes them.** The run
+  routes the spectrometer with `route()` (plesty-lib#59): it writes into
+  `pol-pl/<run_id>/raw/spec` under its bench's folder on the Plesty share and
+  answers with that folder, so a spectrum on bench `platform-a` is recorded as
+  `platform-a/pol-pl/<run_id>/raw/spec/<file>`. The run folder no longer has to
+  be on the share for the spectrometer to write; the run still needs
+  `PLESTY_DATA`. Needs plesty-lib 0.6.0.
+- **The demo's devices are pinned** in `setup.yaml`: the stage is the released
+  `plesty-k10cr1` 0.3.0 (was its `exp` branch) and the spectrometer a fixed
+  commit of its `demo/pol-pl` branch, so a release of this module runs the same
+  demo for as long as it is installed.
+- Requires the released plesty-lib 0.6.0 (was 0.5.0, then its `exp` branch)
+  and, for development, plesty-sdk 0.5.6.
+- `analysis.rotator` also accepts `qwp` once plesty-fss offers it (a
+  quarter-wave plate in front of a fixed polarizer, plesty-fss!10); the
+  configuration test names a rotator neither version knows as its invalid
+  example.
+
+### Fixed
+- The by-hand demo in the README and *Running* works: `-f` goes before
+  `fleet up`, which rejected it (#2); `fleet up` is given a copy of
+  `setup.yaml`, which it would otherwise rewrite (plesty-bench#48), the
+  spectrometer a folder to write in, which `plesty-server` before 0.5 does not
+  give a bench without a share, and the run the two device addresses. The
+  Bench app's welcome needed none of this.
+- The lock takes pillow 13.0.0, brotli 1.2.1 and certifi 2026.10.23, which fix
+  the known vulnerabilities of the versions before.
+
+### Documentation
+- Rebuilt as a guide — *Overview*, *Setup*, *Running*, *Analysis* — around a
+  flowchart of the run and a drawing of the rig. The figures are drawn by the
+  module's own code on the simulated dots of the tests
+  (`scripts/docs_figures.py`); *Analysis* shows a good and a failed fit and how
+  to tell them apart, *Running* covers the demo and the `--run-root` option.
+
+## [0.1.0] - 2026-09-30
+
+The first release, on plesty-lib 0.5.0 and plesty-fss 0.1.0. Its command line
+is built on `ExperimentCLI`, so PLESTY Bench can read its settings and offer it
+on the Marketplace (plesty-bench#15).
+
+### Changed
+- **One shared-data root, `PLESTY_DATA`; ports and the second spelling
+  gone.** The run is given only where this machine sees the shared disk
+  (`PLESTY_DATA`, replacing `PLESTY_DATA_DIR` and `PLESTY_DATA_MOUNT`, which it
+  no longer reads), and every path between machines is relative to that
+  shared point. Runs go to `pol-pl/<run_id>` there (the manifest's and the
+  viewer's root, `RUN_ROOT`); the spectrometer is routed to the run's
+  `raw/spec` and each spectrum is recorded as `pol-pl/<run_id>/raw/spec/<file>`,
+  taking only the file name from the spectrometer. A run directory off the
+  shared disk is refused before anything is measured. `setup.yaml` names no
+  ports or folders — the bench serving each device picks its port and gives
+  the run `HWP_ADDRESS` and `SPEC_ADDRESS` — and both devices run on
+  `bench-local`, the bench without an address; another bench is left in,
+  commented out, as an example. Needs plesty-lib >=0.5.0.dev6, which ships the
+  shared data root; the local path pin on plesty-lib is gone with it.
+- **`fleet.demo.yaml` becomes `setup.yaml`, at the root.** A setup is a fleet
+  file with `benches:` beside the devices: where each bench's agent listens,
+  its token and where it sees the lab's shared data disk, each written as the
+  variable holding it (`${LOCAL_DATA}`) and set in `.env` — the file is
+  committed, so it carries no address, path or token. Every device names its
+  bench (`host_name`: `local`, the machine the experiment runs on, or one of
+  the benches). At start-up the run builds `HWP_ADDRESS` and `SPEC_ADDRESS`
+  from that bench and each device's port, and gives the run where that bench
+  sees the shared data disk, as `PLESTY_DATA` — plesty-lib's setup contract,
+  so the same with or without a bench; a value set by hand in `.env` still
+  wins. A bench writes `.env` when it installs the module. The fleet file's
+  `experiments:` section is gone — the bench declares the experiment, and a
+  second declaration in the module was a copy that could disagree. Needs
+  plesty-lib >=0.5.0.dev6.
+
+### Added
+- **Each dot's analysis is saved with its report.** Beside the fine-structure
+  and line-fit outputs, `analysis/<dot>.report.json` holds what the analyzer
+  found — a sentence, a table of the lines with the splitting in µeV and pm,
+  and the sweep drawn — and the analysis record names it as
+  `report_document`. A reader renders it as HTML or LaTeX without importing
+  plesty-fss (plesty-lib#55).
+- **The module declares how it is run.** `python -m plesty.pol_pl --manifest`
+  prints the run command, the run root, the environment the run reads, the
+  viewer it ships, and every configuration key with its type, unit, bounds and
+  meaning — connecting to nothing, so a console can offer this experiment's
+  settings without being taught anything about it. The declaration is `SCHEMA`
+  in `plesty/pol_pl/__main__.py`, and it and `config/default.yaml` say the same
+  thing: gate e3 fails a key that only one of them knows about.
+
+- **A started run can be paused, cancelled, aborted and annotated** through
+  `plesty.lib.experiment.control` on its run directory. A request takes effect
+  between two angles, where the journal already commits. Pause keeps the stage
+  and the spectrometer connected and where they are; cancel lets the exposure
+  in flight finish and commit; abort does not wait, so the instruments are free
+  at once and that angle re-runs on resume.
+
+- **`fleet.demo.yaml` and `config/demo.yaml`: the experiment runs without a lab, and
+  without a demo mode.** The whole difference is which fleet is brought up. The stage is the
+  released module under `--mock`; the spectrometer is the `demo/pol-pl` branch of
+  `plesty-lightfield-spectrometer`, which answers each acquisition with a spectrum really
+  measured on sample E098-SIL. It reads the run's own `journal.jsonl` to know which step it
+  is answering, so every replaying instrument on a bench stays on one cursor rather than
+  passing values to each other. A step the recording does not hold is refused, never answered
+  with a different spectrum. Nothing was added to this module: no `demo` package, no replay
+  rig, no second CLI, and so nothing here to drift from the measured path.
+
+### Changed
+- **The command line is `plesty.lib.experiment.ExperimentCLI`'s.** `--config`,
+  `--resume`, `--run-root` and `--dry-run` keep their names and behaviour and
+  are now the library's, along with the preflight, the event loop and the
+  graceful stop; `--prominence` stays this module's and is declared in the
+  manifest alongside the configuration key it overrides. Needs
+  `plesty-lib>=0.5.0.dev4`.
+
+- Initial experiment scaffold for `plesty.pol_pl`.
+- `PolPlRig`: the K10CR1 half-wave-plate stage and the LightField spectrometer as one
+  composite device. Plate moves are checked against their target and retried once;
+  acquisitions are never repeated automatically and must produce a new file.
+- `Experiment`: one spectrum per quantum dot per plate angle, then one analysis step per dot
+  that runs `plesty-fss` `FineStructure` over the dot's spectra, records the fine-structure
+  splitting of every line with its validity, and saves the analyzer outputs under
+  `analysis/` in the run (plesty/hub/experiments/plesty-pol-pl#1).
+- The configuration is validated when the experiment is built; a hardware run also requires
+  the shared data disk (`PLESTY_DATA`).
+- `--prominence COUNTS` sets the line-finding threshold of the analysis for one run, in
+  place of `analysis.fit_options.prominence` of the configuration.
+- `python -m plesty.pol_pl.viz`: the spectrum with a marker on every analysed line, the
+  spectral map on a square-root colour scale, and the fine-structure view of each dot, which
+  fills while the sweep is measured and shows each line's result in the line's colour.

plesty_pol_pl-0.2.0.dev1/LICENSE

@@ -0,0 +1,184 @@
+Copyright (C) 2026 Plesty Development Team
+
+This file is part of Plesty.
+
+Plesty is free software: you can redistribute it and/or modify
+it under the terms of the GNU Lesser General Public License as published by
+the Free Software Foundation, either version 3 of the License, or
+(at your option) any later version.
+
+Plesty is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+GNU Lesser General Public License for more details.
+
+You should have received a copy of the GNU Lesser General Public License
+along with Plesty. If not, see <https://www.gnu.org/licenses/> or the copy below.
+
+#########################################################################
+
+                   GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions.
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version.
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+  Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.

plesty_pol_pl-0.2.0.dev1/LICENSES/LGPL-3.0-or-later.txt

@@ -0,0 +1,165 @@
+                   GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions.
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version.
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+  Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.