Differences

This shows you the differences between two versions of the page.

--- en:playground:start [2020/05/07 06:49] – 76.236.30.17
+++ en:playground:start [2025/11/17 17:46] (current) – 2001:a61:61b8:3d01:a5fc:21b2:5f84:caee
@@ Line 1: / Line 1: @@
-==== Optimize! ====
+''$$ Q = CV \tag{1} $$''\\
-{{Optimize_73x76.png}}
+|   ^ Header A ^ Header B ^ Header C ^ Header D |   |
+^ 1  | Left  |   |   | Foo  ^ 1  ^
+^ 2 |  Center  |  value  || ::: ^ 2 ^
+^ 3 |  Right |   |   | ::: ^ 3 ^
-{{:wiki:logo.png}}
+so, latex format not working.\\
-The “Optimize!” button is available in the Automatic Optimization section of the%% %%Optimize%% %%tab. This button displays the Local Optimization tool for automatic optimization of the current optical system.
+$A$
-{{Optimize_2_611x232.png}}
+$$
-**//%%Settings:%%//**
+\begin{aligned}
-**Algorithm**%% %%Local Optimization uses a Damped Least-Squares or Orthogonal Descent algorithm to improve or modify a design to meet specific conditions.
+  C \propto & \space A \\ C \propto & \space \frac{1}{d}
-**Damped Least Squares (DLS)**%% %%uses numerically computed derivatives to determine a direction in solution space which produces a design with a lower merit function. This gradient method has been developed specifically for optical system design and is recommended for all optimization problems.
+  \end{aligned}
-**Orthogonal Descent (OD)**%% %%uses an orthonormalization of the variables and discrete sampling of solution space to reduce the merit function. The OD algorithm does not compute numerical derivatives of the merit function. For systems with inherently noisy merit functions, such as non-sequential systems, OD will usually outperform DLS. For a discussion of a similar algorithm, see S. Kudaev, P. Schreiber, “Automated optimization of non-imaging optics for luminaries”, in Optical Design and Engineering II; Laurent Mazuray, Rolf Wartmann, Eds., Proc. SPIE 5962, p. 87-95 (2005).
+$$
-**Note**%% %%that both DLS and OD are local optimization algorithms whose final results depend upon the starting point. For global optimization, see “Global Optimizers”.
+Ceci est un test !
-**# of Cores**%% %%Selects the number of cores over which to spread the optimization task. More than 1 may be selected, even on a single CPU computer, in which case the single CPU will time share the multiple simultaneous tasks. The default is the number of processors detected by the operating system.
+<code python test.py>
+import os
+os.getcwd()
+print("hello world!")
+</code>
-**Cycles**%% %%Select the number of optimization cycles. 1 Cycle Executes a single optimization cycle, 5 Cycles Executes 5 optimization cycles, etc. Inf. Cycles Executes optimization cycles in an infinite, continuous loop until “Stop” is pressed.
+====== Hello ! ======
-**Selecting Automatic%% %%**will cause the optimizer to run until no progress is being made. Automatic mode is highly recommended. The time required to run a given optimization cycle varies enormously with the number of variables, the complexity of the system, the number of solves, the number of operands, and of course the computer speed. If the cycle is taking too long, or if it appears to be hung up, or if you feel the design is not progressing adequately, click on Stop to end the optimization run.
+| Hi |   |
+|   |   |
-**Auto Update**%% %%If checked, OpticStudio will automatically update and redraw all open windows at the end of each optimization cycle. This allows monitoring of the optimization progress using any analysis feature. Note that the fastest rate at which the windows can update is once every 5 seconds, in order to maintain responsivity of the user interface during the updates.
+<code xojonnn fff 123>
+Here we go again
+</code>
-**Start%% %%**Starts the optimization.
+| dfgdfg  |   |
+| abcvv  | gdfgdf  |
-**Stop**%% %%Stops a running optimization, and returns control back to the dialog box.
+Das ist ein Test. **Schauen wir mal wie fett geht. **
-**Save**%% %%Saves the current settings to the OpticStudio configuration file.
+Sieht aus wie der alte Editor → Ah, man muss erst auf "visual Editor" umschalten - Diese Bezeichnung erinnert an Mediawiki :-).
-**Load**%% %%Loads the last saved settings.
+Ok, wie bekomme ich eine Grafik eingebunden? ← Indem man oben das Icon mit dem Bilderrahmen klickt.
-**Reset**%% %%Resets all settings to default.
+===== heading 2 =====
-**//%%Discussion:%%//**
+[[Ficiher@iap.fr|Ficiher]]
-The Local Optimization (or simply, “Optimization”) feature provided by OpticStudio is quite powerful, and is capable of improving lens designs given a reasonable starting point and a set of variable parameters. Variables can be curvatures,%% thicknesses%%,%% glasses%%, conics,%% parameter data%%, extra data, and any of the numeric multi-configuration data. OpticStudio uses either an actively damped least squares or an orthogonal descent algorithm. The algorithms are capable of optimizing a merit function composed of weighted target values; these target values are called “operands”. OpticStudio has several different default merit functions which can be changed easily using the Merit Function Editor. For details on this procedure see “Modifying the merit function.”
+[[link|Edit section]]
-When the optimization begins, OpticStudio first updates the system merit function. If any of the operands cannot be computed, the optimization cannot begin, and an error message will be displayed. Operands cannot be computed if they require the tracing of rays which miss surfaces or which undergo%% total internal reflection (TIR) %%at an index boundary. If such an error message appears, usually the starting lens prescription is in error, or the ray targets are incorrectly defined (this will not happen with the default merit functions, but might happen with user defined rays). OpticStudio can automatically recover if the merit function cannot be evaluated during the course of optimization; only the starting system need be adequate to compute all operands in the merit function.
+| {{https://wiki.cocube.fun/en/activities/cocube_basic_00_start-en/image_upgrade_cocube.png}} |   |
+|   |   |
-See%% Optimization Overview %%for a full discussion of building merit functions, setting variables, and using the optimization feature.
+|   |   |
+|   |   |
-See also
+|   |   |
+|   |   |
-**Next:**
+# Heading
-Remove All Variables\\
+**Testing this editor**
-Great editor !!
+<code python file.py>
+Here is my code
-I wish we could paste images that can be saved automatically.
+Testing Test class py
+</code>
-I wish we could use basic HTML tags, such as H1, H2, etc for font sizes.
+|   |   |   |   |
+| Test Table | Test | Test |   |
+| 1.2.3.8-) |   |   | sdf |
+|   |   | sdf |   |
-I wish I could but I don't want to.
+==== heading 3 ====
-huh!
+Looks great - at frist glance ... 🤔
--O
+===== Deleted content, now visual editor appears to function =====
-  - This is fine.
+**One **two three four
-  - this is nice
-  - <code ->
+  * Ctrl-I / Ctrl-B would be nice
-this is a test.
+Table support is handy
+| qds  | qsdq  | sdqs |
+|   |   |   |
+|   |   |   |
+Testing ...
+==== Headline ====
+ Achtergrond
+//Locales// worden gebruikt door glibc en andere locale-aware programma's om text, datum, valuata, soorteervolgorde, etc. aan te passen aan locale gebruiken.
+Het behelst een systeem met zo'n drie onderdelen:
+  * //Local Names:// Specificaties van talen/landen
+  * //System variables:// Zoals //taal//, //valuta//, etc.
+  * //Configuraties:// Dit is waar local names aan system variables toegewezen worden. Dat kan ik verschillende bestanden en op verschillende manieren.
+==== Locale Names ====
+//Locales// of //local names// zijn in de vorm [1]
+<code ->
+language[_territory].[codeset][@modifier]
 </code>
-====== Nothing to see here. ======
+waarbij geldt:
-| First column  | Second column  |
+  * ''language'' - ISO 639 language code
-|   |   |
+  * ''territory'' - ISO 3166 country code
-| Last row  | {{https://thumbs.dreamstime.com/z/livre-de-coloriage-pangolin-87544118.jpg?100x100|Pangolin}}  |
+  * ''codeset'' - ISO-8859-1- of UTF-8-identifier. In de praktijk gebruik ik //altijd// een UTF-8-identifier
+  * ''modifer'' - Geen idee. Misschien zijn de aanduidingen ''@euro'' op sommige regels in ''/etc/locale.gen'' hier een voorbeeld van.
-><code ->
+Alle beschikbare locales kun je opvragen mbv. ''less /etc/locale.gen''. Dit zijn de NL-gerelateerde locales:
--o
+<code ->
+nl_AW UTF-8
+nl_BE ISO-8859-1
+nl_BE.UTF-8 UTF-8
+nl_BE@euro ISO-8859-15
+nl_NL ISO-8859-1
+nl_NL.UTF-8 UTF-8
+nl_NL@euro ISO-8859-15
 </code>
->\\ \\ \\ \\ \\ \\ \\ \\ 8-o
->>((
-))
+Merk op dat er niet zoiets bestaat als //en_NL// (Engelstalig + Nederland). Ik heb me er bij neergelegd dat ik qua taal //en_US UTF-8// gebruik.
->\\
->\\
+Dit zijn de instellen op één van m'n computers. Dit was voordat ik de //locale// had geconfigureerd. Dit overzicht krijg je met het commando ''locale'':
->\\
->\\
+<code ->
->\\
+LANG=C
->((
+LANGUAGE=
+LC_CTYPE="C"
+LC_NUMERIC=en_US.UTF-8
+LC_TIME=en_US.UTF-8
+LC_COLLATE="C"
+LC_MONETARY=en_US.UTF-8
+LC_MESSAGES="C"
+LC_PAPER=en_US.UTF-8
+LC_NAME=en_US.UTF-8
+LC_ADDRESS=en_US.UTF-8
+LC_TELEPHONE=en_US.UTF-8
+LC_MEASUREMENT=en_US.UTF-8
+LC_IDENTIFICATION=en_US.UTF-8
+LC_ALL=
+</code>
-))
+.. 2.. 3.. Lorem Ipsum** lorem ipsum**
->\\
->\\
->\\
->\\
->\\
->\\
->\\
->\\
->\\
->\\
->\\
->\\
->\\
->\\
->\\
->\\
->\\
->\\
->\\
->\\
->\\
->\\
->((
-))
+~~NOTOC~~
->\\
->\\
->\\
->\\
->\\
->\\
->\\
->((
-))