repo
stringlengths 26
115
| file
stringlengths 54
212
| language
stringclasses 2
values | license
stringclasses 16
values | content
stringlengths 19
1.07M
|
|---|---|---|---|---|
https://github.com/piepert/philodidaktik-hro-phf-ifp | https://raw.githubusercontent.com/piepert/philodidaktik-hro-phf-ifp/main/src/parts/ephid/descartes/main.typ | typst | Other | #import "/src/template.typ": *
= #ix("Descartes, René") in Verbindung mit dem #ix("Rahmenplan MV", "Rahmenplan")
#author[<NAME>]
Zu jedem Thema wird eine inhaltliche Erklärung vorangeschoben, in der Descartes Ausgangsproblem erklärt, seine Argumentation dargestellt und sein Fazit beschrieben wird. Darauf folgen Ideen, welche der Themen im Rahmenplan auf welche Weise mit Themen bei Descartes verbunden werden können.
#include "methodischer_zweifel.typ"
#include "cogito_argument.typ"
#include "denkendes_ding.typ"
#include "wachsbeispiel.typ"
#include "fremdpsychische.typ" |
https://github.com/7sDream/fonts-and-layout-zhCN | https://raw.githubusercontent.com/7sDream/fonts-and-layout-zhCN/master/chapters/02-concepts/dimension/latin-heights.typ | typst | Other | #import "/lib/draw.typ": *
#import "/lib/glossary.typ": tr
#import "/template/theme.typ": theme
#import "/template/lang.typ": armenian
#let start = (0, 0)
#let end = (1000, 400)
#let basex = 200
#let basey = 120
#let base = (basex, basey)
#let ascender = 242
#let cap = 228
#let xheight = 172
#let decender = -80
#let width = 780
#let graph = with-unit((ux, uy) => {
// mesh(start, end, (100, 100), stroke: 1 * ux + gray)
let line-left = basex - 30
for y-offset in (ascender, cap, xheight, 0, decender) {
let y = basey + y-offset
segment(
(if y-offset != 0 { line-left } else { basex }, y),
(base.at(0) + width, y),
stroke: 2 * ux + theme.main,
)
}
rect(
(basex, basey + ascender),
width: width,
height: ascender - decender,
)
txt([#tr[ascender]：1556], (line-left, basey + ascender), anchor: "rb", size: 20 * ux,dx: -10, dy: -2)
txt([#tr[cap height]：1462], (line-left, basey + cap), anchor: "rc", size: 20 * ux,dx: -10)
txt([#tr[x-height]：1096], (line-left, basey + xheight), anchor: "rc", size: 20 * ux,dx: -10)
txt([#tr[decender]：-492], (line-left, basey + decender), anchor: "rb", size: 20 * ux,dx: -10)
txt([Hxgh], base, anchor: "lb", size: 320 * ux)
})
#canvas(end, start: start, width: 100%, graph)
|
https://github.com/mariunaise/HDA-Thesis | https://raw.githubusercontent.com/mariunaise/HDA-Thesis/master/pseudocode/bach_find_best_appr.typ | typst | #import "@preview/lovelace:0.3.0": *
#pseudocode-list(booktabs: true, numbered-title: [OptimalWeights to approximate $bold(cal(o))$])[
+ *inputs*:
+ $bold(y)$ input values for linear combinations
+ $bold(cal(o))$ list of optimal points
+ *output*: $(bold(h), z_"opt")$
//+ n number of summands in linear combination
+ *calculate* all possible linear combinations $bold(z)$ with @eq:z_eq
+ *calculate* matrix $bold(cal(A))$ with $a_"ij" = abs(z_i - cal(o)_j)$
+ *return* weights $bold(h)$ for $z_"opt" = op("argmin")(bold(cal(A)))$ and $z_"opt"$
]
|
|
https://github.com/Myriad-Dreamin/tinymist | https://raw.githubusercontent.com/Myriad-Dreamin/tinymist/main/crates/tinymist-query/src/fixtures/semantic_tokens/typst_lsp_issue_264.typ | typst | Apache License 2.0 | /*
??
?
*/
```rust
let x: usize = 1;
``` |
https://github.com/typst/packages | https://raw.githubusercontent.com/typst/packages/main/packages/preview/fletcher/0.1.1/test/test.typ | typst | Apache License 2.0 | #import "@preview/cetz:0.1.2"
#import "/src/exports.typ": *
#import "/src/marks.typ": *
#set page(width: 10cm, height: auto)
#show heading.where(level: 1): it => pagebreak(weak: true) + it
= Arrow heads
Compare to symbols $#sym.arrow$, $#sym.arrow.twohead$, $#sym.arrow.hook$, $#sym.arrow.bar$
#arrow-diagram(
debug: 0,
spacing: (10mm, 5mm),
{
for i in (0, 1, 2) {
let x = 2*i
let bend = 40deg*i
(
(marks: ("harpoon", "harpoon'")),
(marks: ("head", "head")),
(marks: ("tail", "tail")),
(marks: ("twotail", "twohead")),
(marks: ("hook", "head")),
(marks: ("hook", "hook'")),
(marks: ("bar", "bar")),
(marks: (none, none), extrude: (2.5,0,-2.5)),
(marks: ("head", "head"), extrude: (1.5,-1.5)),
(marks: ("tail", "tail"), extrude: (1.5,-1.5)),
(marks: ("bar", "head"), extrude: (2,0,-2)),
(marks: ("twotail", "twohead"), extrude: (1.5,-1.5)),
).enumerate().map(((i, args)) => {
conn((x, -i), (x + 1, -i), ..args, bend: bend)
}).join()
}
})
= Arrow head shorthands
$
#for i in (
"->",
"<-",
"<->",
"<=>",
"|->",
"|=>",
">->",
"->>",
"hook->",
"hook'--hook",
"|=|",
">>-<<",
"harpoon-harpoon'",
"harpoon'-<<",
"<--hook'",
"|..|",
"hooks--hooks",
) {
$ #block(inset: 2pt, fill: white.darken(5%), raw(i))
&= #arrow-diagram(conn((0,0), (1,0), ..parse-arrow-shorthand(i))) \ $
}
$
= Connectors
#arrow-diagram(
debug: 0,
cell-size: (10mm, 10mm),
node((0,1), $X$),
node((1,1), $Y$),
node((0,0), $Z$),
conn((0,1), (1,1), marks: (none, "head")),
conn((0,0), (1,1), $f$, marks: ("hook", "head"), dash: "dashed"),
conn((0,1), (0,0), marks: (none, "twohead")),
conn((0,1), (0,1), marks: (none, "head"), bend: -120deg),
)
= Arc connectors
#arrow-diagram(
cell-size: 3cm,
{
node((0,0), "from")
node((1,0), "to")
for θ in (0deg, 20deg, -50deg) {
conn((0,0), (1,0), $#θ$, bend: θ, marks: (none, "head"))
}
})
#arrow-diagram(
debug: 3,
node((0,0), $X$),
node((1,0), $Y$),
conn((0,0), (1,0), bend: 45deg, marks: ("head", "head")),
)
#for (i, to) in ((0,1), (1,0), (calc.sqrt(1/2),-calc.sqrt(1/2))).enumerate() {
arrow-diagram(debug: 0, {
node((0,0), $A$)
node(to, $B$)
let N = 6
range(N + 1).map(x => (x/N - 0.5)*2*120deg).map(θ => conn((0,0), to, bend: θ, marks: ("tail", "head"))).join()
})
}
= Defocus
#let around = (
(-1,+1), ( 0,+1), (+1,+1),
(-1, 0), (+1, 0),
(-1,-1), ( 0,-1), (+1,-1),
)
#grid(
columns: 2,
..(-10, -1, -.25, 0, +.25, +1, +10).map(defocus => {
((7em, 3em), (3em, 7em)).map(((w, h)) => {
align(center + horizon, arrow-diagram(
node-defocus: defocus,
node-pad: 0pt,
{
node((0,0), rect(width: w, height: h, inset: 0pt, align(center + horizon)[#defocus]))
for p in around {
conn(p, (0,0))
}
}))
})
}).join()
)
= Label placement
Default placement above the line.
#arrow-diagram(
// cell-size: (2.2cm, 2cm),
spacing: 2cm,
debug: 3,
{
for p in around {
conn(p, (0,0), $f$)
}
})
#arrow-diagram(spacing: 1.5cm, {
for (i, a) in (left, center, right).enumerate() {
for (j, θ) in (-30deg, 0deg, 50deg).enumerate() {
conn((2*i, j), (2*i + 1, j), label: a, "->", label-side: a, bend: θ)
}
}
})
= Crossing connectors
#arrow-diagram({
conn((0,1), (1,0))
conn((0,0), (1,1), crossing: true)
conn((2,1), (3,0), "|-|", bend: -20deg)
conn((2,0), (3,1), "<=>", crossing: true, bend: 20deg)
})
= Coord callback
// #arrow-diagram({
// node((1,1), "hi")
// conn((1,1), (1,2))
// resolve-coords((1, 2), (1,1), callback: (p1, p2) => {
// cetz.draw.circle(p1, radius: 5pt, stroke: red)
// })
// })
= `conn()` argument shorthands
#arrow-diagram(
conn((0,0), (1,1), "->", "double", bend: 45deg),
conn((1,0), (0,1), "->>", "crossing"),
conn((1,1), (2,1), $f$, "|->"),
conn((0,0), (1,0), "-", "dashed"),
)
= Diagram-level options
#arrow-diagram(
node-stroke: black,
node-fill: green.lighten(80%),
node((0,0), $A$),
node((1,1), $sin compose cos compose tan$, fill: none),
node((2,0), $C$),
node((3,0), $D$, shape: "rect"),
conn((0,0), (1,1), "->", bend: -45deg),
conn((2,0), (1,1), "<-"),
)
= CeTZ integration
#arrow-diagram(
node((0,0), $A$, stroke: 1pt),
node((2,1), [Bézier], stroke: 1pt),
render: (grid, nodes, conns, options) => {
cetz.canvas({
arrow-diagrams.draw-diagram(grid, nodes, conns, options)
let n1 = arrow-diagrams.find-node-at(nodes, (0,0))
let p1 = arrow-diagrams.get-node-anchor(n1, 0deg)
let n2 = arrow-diagrams.find-node-at(nodes, (2,1))
let p2 = arrow-diagrams.get-node-anchor(n2, -90deg)
let c1 = cetz.vector.add(p1, vector-polar(20pt, 0deg))
let c2 = cetz.vector.add(p2, vector-polar(70pt, -90deg))
arrow-diagrams.draw-arrow-cap(p1, 180deg, (thickness: 1pt, paint: black), "head")
cetz.draw.bezier(p1, p2, c1, c2)
})
}
)
= Node bounds
#arrow-diagram(
debug: 2,
node-outset: 5pt,
node-pad: 5pt,
node((0,0), `hello`, stroke: 1pt),
node((1,0), `there`, stroke: 1pt),
conn((0,0), (1,0), "<=>"),
)
|
https://github.com/Henriquelay/pathsec-checker | https://raw.githubusercontent.com/Henriquelay/pathsec-checker/main/presentation/figures/addition_boxes.typ | typst | #set page(width: auto, height: auto, margin: (x: 0pt, y: 0pt))
#set text(font: "DejaVu Sans Mono")
#let myswitch(name, digest, expected) = {
box[
#table(
columns: 2,
fill: if (digest == expected) {
lime
} else {
red
},
align: (right, left),
[name], [#name],
[digest], [#digest],
[expected], [#expected],
)
]
}
#table(
columns: 4,
stroke: none,
inset: 3pt,
myswitch([e1], [0XABADCAFE], [0XABADCAFE]),
myswitch([s1], [0X432CF798], [0X432CF798]),
myswitch([s2], [0XE04DF688], [0XE04DF688]),
myswitch([s3], [0XE8F0142C], [0XE8F0142C]),
myswitch([s4], [0XB452022A], [0XB452022A]),
myswitch([s5], [0X4450D2D2], [0X4450D2D2]),
myswitch([s555], [0X5B0FCE3E], [0XE9367B57]),
myswitch([s6], [0X5B0FCE3E], [0XE9367B57]),
myswitch([s7], [0X03E1E388], [0X991182C1]),
myswitch([s8], [0X2138FFD3], [0X35E72E11]),
myswitch([s9], [0X1EF2CBBE], [0XAA152EB9]),
myswitch([s10], [0X99C5FE05], [0X1A1573E7]),
)
#pagebreak()
#table(
columns: 4,
stroke: none,
inset: 3pt,
myswitch([e10], [0XBADDC0DE], [0XBADDC0DE]),
myswitch([s10], [0X5F9298A3], [0X5F9298A3]),
myswitch([s9], [0X4C43786D], [0X4C43786D]),
myswitch([s8], [0X0D614B06], [0X0D614B06]),
myswitch([s7], [0X1DD20B9C], [0X1DD20B9C]),
myswitch([s6], [0X0B1BD6C6], [0X0B1BD6C6]),
myswitch([s5], [0X45E5A48F], [0X45E5A48F]),
myswitch([s4], [0XCDA3CE15], [0XCDA3CE15]),
myswitch([s3], [0XF7F2FDF1], [0XF7F2FDF1]),
myswitch([s2], [0X4CCC369F], [0X4CCC369F]),
myswitch([s1], [0X5A2481CB], [0X5A2481CB]),
)
|
|
https://github.com/chickbone/hypergraph | https://raw.githubusercontent.com/chickbone/hypergraph/master/functions.typ | typst | #let qed = [
#align(end,
rect(width: 9pt,height: 9pt,)
)
#v(10pt)
]
#let numbered_eq(content) = math.equation(
block: true,
numbering: "(1)",
content,
)
#let big_title(content) = [
#v(10pt)
#align(center, text(17pt)[
#content
])
#v(15pt)
]
#let theorem-number = counter("theorem-number")
#let theorem(title: none, kind: "定理", body) = {
let head_num = context(counter(heading).get()).first()
let thm_num = theorem-number.display()
let title-text = {
if title == none {
emph[#kind #head_num.#thm_num ]
}
else {
emph[#kind #head_num.#thm_num【#title】]
}
}
box(stroke: (left: 1pt), inset: (left: 5pt, top: 2pt, bottom: 5pt))[
#title-text #h(0.5em)
#body
]
theorem-number.step()
}
#let proof(body) = list(marker: "証:")[
#body
#qed
]
#let comb(a,b) =$vec(#a,#b)$
#let rGrph(r) =$bold("Grph")_(#r)$
#let power(A) =$frak(P)(#A)$
#let rgraph(r) = [$#r thin hyph.nobreak$graph]
#let krgraph(k,r) = [$#k$部$#r thin hyph.nobreak$graph] |
|
https://github.com/sofianedjerbi/ResumeOld | https://raw.githubusercontent.com/sofianedjerbi/ResumeOld/main/modules/languages.typ | typst | Apache License 2.0 | #import "../brilliant-CV/template.typ": *
#cvSection("Langues")
#let lightbold(str) = text(weight: 501, str)
- #lightbold("Français:") Langue maternelle
- #lightbold("Anglais:") Niveau C1 (oral & écrit) |
https://github.com/MasterEvarior/typst-cv | https://raw.githubusercontent.com/MasterEvarior/typst-cv/main/template/template.typ | typst | MIT License | //Config vars
#set list(indent: 1em)
#let par_space = 0.5em
#let sep_space = par_space + 0.2em
#let photo_size = 11em
#let colum_gutter = 3em
#let row_gutter = 1.5em
#let icon = (name, raise: false) => box(
baseline: if raise { 0.03em } else { 0.15em },
inset: (right: 0.5em),
image(
height: 1em,
"assets/svg/" + name + ".svg"
)
)
#let template(doc, color, name, photo, profile, personal_info) = {
set page(margin: (x: 1.5cm, y: 1cm))
set text(font: "Arial", size: 11pt)
set par(justify: true, leading: 0.5em)
set table(inset: 0pt,stroke: none)
show heading.where(level: 1): i => {
set align(left)
let title = smallcaps(i.body)
set block(above: 1em)
set text(weight: "light", size: 1.2em, fill: rgb(0, 0, 0))
stack(
dir: ttb,
spacing: 2mm,
title,
line(length: 100%, stroke: color + 2pt)
)
}
show heading.where(level: 2): i => {
set align(left)
let title = smallcaps(i.body)
set block(above: 0.8em)
set text(weight: "light", size: 1.1em, fill: color)
title
}
align(left)[
#smallcaps(text(size: 2.5em, fill: color)[#name]) \
]
table(
columns: 2,
column-gutter: colum_gutter,
row-gutter: row_gutter,
[
#align(left)[
= #icon("person") Personal Profile
#text("A skilled software developer with a track record of creating and maintaining high-quality software. Enthusiastic to learn new technologies and skills. Currently seeking a new professional challenge.")
]
#table(
columns: 2,
column-gutter: colum_gutter,
row-gutter: 1em,
..personal_info.map(pi => (
[
#icon(pi.service) #pi.display
]
)).flatten()
)
],
[
#align(right)[
#{
if photo != none {
linebreak()
image("assets/img/" + photo, width: photo_size, height: photo_size)
}
}
]
]
)
doc
}
// Format start and end dates.
#let format_date(start_date: none, end_date: none) = {
let date = {
if end_date == none {
start_date
} else if start_date == none {
end_date
} else {
start_date + " - " + end_date
}
}
[*#date*]
}
// Format locations.
#let format_location(location) = {
[_#block(above: sep_space, icon("location") + location )_]
}
// General entry that is split into a left and right half (for experience and education).
#let cv_entry(left_content: none, right_content: none) = {
grid(
columns: (11fr, 6fr),
column-gutter: 1cm,
{
set align(left)
left_content
},
{
set align(right)
right_content
}
)
}
// Entry for education.
#let education_entry(degree, university, degree_title: none, description: none, start_date: none, end_date: none, location: none) = {
cv_entry(
left_content: {
if degree_title != none {
[*#degree_title*] + " "
} + [*#degree*] + [ _(#university)_ ] + block(above: sep_space, par[#description])
},
right_content: {
format_date(start_date: start_date, end_date: end_date)
if location != none {
"\n" + format_location(location)
}
}
)
}
// Entry for work.
#let work_entry(role, company, tasks: none, start_date: none, end_date: none, location: none) = {
cv_entry(
left_content: {
[*#role*] + block(above: sep_space, text[_(#company)_])
if tasks != none {
let tasks_list = []
for task in tasks {
tasks_list += [- #task]
}
tasks_list
}
},
right_content: {
format_date(start_date: start_date, end_date: end_date)
if location != none {
"\n" + format_location(location)
}
}
)
}
// Entry for skills
#let skill_entry(skills) = {
[== Technologies]
table(
columns: 4,
gutter: 1fr,
column-gutter: colum_gutter,
row-gutter: row_gutter,
align: left + horizon,
..skills.map(s => (
[ #icon(s.icon, raise: if s.keys().contains("raise") { s.raise } else { false }) #s.name]
)).flatten()
)
}
// Entry for references
#let references_entry(refs) = {
table(
columns: (auto, 1fr, auto),
column-gutter: colum_gutter,
row-gutter: row_gutter,
..refs.map(r => (
[ #r.name ],
[ #r.role ],
[
#if r.email != none {[
#icon("envelope") #link("mailto:" + r.email)
]}
\
#if r.phone != none {[
#icon("phone") #link("tel:" + r.phone)
]}
],
)).flatten()
)
}
#let interests_entry(interests) = {
table(
columns: 2,
column-gutter: colum_gutter,
row-gutter: row_gutter,
..interests.map( i => (
[ #i.name],
[ #i.description]
)).flatten()
)
}
#let misc_entry(miscellaneous) = {
table(
columns: (auto, 1fr),
column-gutter: colum_gutter,
row-gutter: 1em,
..miscellaneous.map(m => (
[ - #m.label ],
[ #m.value ],
)).flatten()
)
}
#let languages_entry(languages) = {
[== Natural Languages ]
table(
columns: (auto, 1fr, auto),
column-gutter: 1em,
align: horizon,
row-gutter: 1em,
..languages.map(l => {
(
[ #l.name ],
[
#let level = 0
#while level < 10 {
level = level + 1
let color = if (level > l.level) {
luma(227)
} else {
luma(0)
}
box(
fill: color,
height: .3em,
width: 1fr,
)
}
],
[ #l.acquisition ]
)
}).flatten()
)
} |
https://github.com/thanhdxuan/dacn-report | https://raw.githubusercontent.com/thanhdxuan/dacn-report/master/Lab02/main.typ | typst | #set page(
paper: "a4",
header: { include "/components/header.typ" },
footer: { include "/components/footer.typ" },
margin: (
top: 30mm,
bottom: 20mm,
left: 30mm,
right: 20mm,
),
)
#let m = yaml("/metadata.yml")
#let fonts = m.at("fonts")
#set document(title: m.at("tiêu đề"), author: m.at("<NAME>").map(s => s.at("tên")))
#set text(font: fonts.at("text"), lang: "vi")
#show raw: set text(font: fonts.at("monospace"))
#show raw.where(block: true): set block(fill: gray.lighten(90%), width: 100%, inset: (x: 1em, y: 1em))
#show link: it => {
set text(fill: blue)
underline(it)
}
#set heading(numbering: "1.1.1")
#show heading: it => {
it
v(.5em)
}
#set table(
)
#import "/components/latex.typ"
#show "LaTeX": latex.LaTeX
#{ include "/contents/00.typ" } |
|
https://github.com/Daillusorisch/HYSeminarAssignment | https://raw.githubusercontent.com/Daillusorisch/HYSeminarAssignment/main/template/components/front-matter.typ | typst | #import "../utils/style.typ": *
#let front-matter(
content
) = {
set page(
footer: {
set align(center)
text(
font: 字体.宋体,
size: 字号.五号,
counter(page).display("I")
)
}
)
counter(page).update(1)
show par: set block(spacing: 1.5em)
content
}
|
|
https://github.com/Az-21/typst-material-you | https://raw.githubusercontent.com/Az-21/typst-material-you/main/README.md | markdown | Apache License 2.0 | # Typst Material You
🎨 Utility to parse material you theme for typst
## Material You Palettes
### Blue
<p align="center">
<a href="https://github.com/Az-21/typst-material-you/blob/main/Sample/blue.typ">Blue M3 Palette ↗️</a>
</p>
### Green
<p align="center">
<a href="https://github.com/Az-21/typst-material-you/blob/main/Sample/green.typ">Green M3 Palette ↗️</a>
</p>
### Purple
<p align="center">
<a href="https://github.com/Az-21/typst-material-you/blob/main/Sample/purple.typ">Purple M3 Palette ↗️</a>
</p>
## Usage Guide
The above samples are pre-parsed and ready-to-import in your typst project. If you'd like to generate your custom palette, follow these steps.
### 1. Generate Custom Material You Palette
- Go to https://m3.material.io/theme-builder#/custom
- Set color seeds as per your preference (see left hand panel)
- After previewing colors on the website, export as `.kt` file
- Click on `Export` button on the top panel
- Export > Jetpack Compose (Theme.kt)
- Open the downloaded `.zip` archive and copy out `Color.kt` file
- `Color.kt` can be found in `ui/theme/` folder
- Keep hold of `Color.kt` until the final step
> [!TIP]
> You can rename `Color.kt`. Just preserve the `.kt` extension.
### 2. Install .NET 8.0 Runtime
- Go to https://dotnet.microsoft.com/en-us/download/dotnet/8.0
- Download and install the latest .NET 8.0 **runtime** based on your OS and CPU architecture
### 3. Download Typst Material You
- Download the `.7z` file from https://github.com/Az-21/typst-material-you/releases
- Extract using [7-zip](https://www.7-zip.org/) or [NanaZip](https://github.com/M2Team/NanaZip/releases)
- Copy-paste the `Color.kt` file inside the `Input` folder
- Run `M3Parser.exe`
- Program will generate a ready-to-import color palette in `Output` folder
### 4. Import in Typst Project
```typst
#import "color.typ": m3dark, m3light
#box(width: 32pt, height: 32pt, fill: m3light.primary)
#box(width: 32pt, height: 32pt, fill: m3dark.onTertiary)
```
|
https://github.com/Error-418-SWE/Documenti | https://raw.githubusercontent.com/Error-418-SWE/Documenti/src/3%20-%20PB/Documentazione%20esterna/Analisi%20dei%20Requisiti/Analisi%20dei%20Requisiti.typ | typst | #import "/template.typ": *
#show: project.with(
title: "Analisi dei Requisiti",
subTitle: "Warehouse Management 3D (WMS3)",
authors: (
"<NAME>",
"<NAME>",
"<NAME>",
"<NAME>",
),
showLog: true,
isExternalUse: true,
);
= Introduzione
== Scopo del documento
Il presente documento descrive i casi d'uso e i requisiti del progetto _Warehouse Management 3D_, elaborati a partire dal capitolato C5 proposto da Sanmarco Informatica S.p.A e assegnato all'organizzazione dal Committente.
== Glossario
#glo_paragrafo
== Riferimenti <riferimenti>
=== Riferimenti a documentazione interna <riferimenti-interni>
- Documento #glo_v: \
_#link("https://github.com/Error-418-SWE/Documenti/blob/main/3%20-%20PB/Glossario_v" + glo_vo + ".pdf")_
#lastVisitedOn(25, 02, 2024)
- Documento #ndp_v: \
_#link("https://github.com/Error-418-SWE/Documenti/tree/main/3%20-%20PB/Documentazione%20interna/Norme%20di%20Progetto_v" + ndp_vo + ".pdf")_
#lastVisitedOn(25, 02, 2024)
=== Riferimenti normativi <riferimenti-normativi>
- Regolamento del progetto didattico: \
_#link("https://www.math.unipd.it/~tullio/IS-1/2023/Dispense/PD2.pdf")_
#lastVisitedOn(13, 02, 2024)
- Standard ISO/IEC/IEEE 12207:2017: \
_#link("https://www.iso.org/obp/ui/en/#iso:std:iso-iec-ieee:12207:ed-1:v1:en")_
#lastVisitedOn(13, 02, 2024)
- Standard ISO/IEC/IEEE 29148:2018: \
_#link("https://ieeexplore.ieee.org/servlet/opac?punumber=8559684")_
#lastVisitedOn(13, 02, 2024)
- SWEBOK Chapter 1: Software Requirements: \
_#link("http://swebokwiki.org/Chapter_1:_Software_Requirements")_
#lastVisitedOn(13, 02, 2024)
=== Riferimenti informativi <riferimenti-informativi>
- Verbali interni;
- Verbali esterni;
- Capitolato "Warehouse Management 3D" (C5) di _Sanmarco Informatica S.p.A._: \
_#link("https://www.math.unipd.it/~tullio/IS-1/2023/Progetto/C5.pdf")_
#lastVisitedOn(13, 02, 2024)
- Documentazione Three.js: \
_#link("https://threejs.org/docs/index.html")_
#lastVisitedOn(13, 02, 2024)
- Analisi dei requisiti: \
_#link("https://www.math.unipd.it/~tullio/IS-1/2023/Dispense/T5.pdf")_
#lastVisitedOn(13, 02, 2024)
- Analisi e descrizione delle funzionalità, Use Case e relativi diagrammi (UML): \
_#link("https://www.math.unipd.it/~rcardin/swea/2022/Diagrammi%20Use%20Case.pdf")_
#lastVisitedOn(13, 02, 2024)
- WebGL 2.0 Specification: \
_#link("https://registry.khronos.org/webgl/specs/latest/2.0/")_
#lastVisitedOn(13, 02, 2024)
#pagebreak()
= Descrizione del prodotto
== Obiettivi del prodotto
Il prodotto software oggetto di questo documento è un gestionale di magazzino (WMS, _"Warehouse Management Software"_) che offre una visualizzazione 3D del magazzino ed un set di funzionalità logistiche di base.
== Ambito del prodotto
Il prodotto software oggetto di questo documento è denominato *WMS3*, un gestionale di magazzino che offre le seguenti funzionalità:
- visualizzazione tridimensionale di un magazzino, con possibilità di muovere la vista;
- visualizzazione delle informazioni della merce presente in magazzino;
- esecuzione di operazioni CRUD non persistenti sugli scaffali;
- caricamento dei dati relativi alle merci da un database SQL;
- emissione di richieste di movimentazione della merce all'interno del magazzino;
- filtraggio e ricerca delle merci con rappresentazione grafica dei risultati;
- importazione di planimetrie in formato SVG.
I gestionali di magazzino tradizionali presentano una serie di problematiche:
- rappresentazione 2D del contenuto del magazzino;
- software pensato per un uso esclusivamente desktop;
- interfaccia di gestione complessa (@wms-tradizionale), inadatta all'uso tramite touchscreen o da parte di personale non tecnico;
- interpretazione dei dati e delle viste laboriosa e soggetta ad errore umano;
- tempi di formazione del personale lunghi a causa della complessità degli strumenti.
#figure(
image("./imgs/wms-tradizionale.jpg", format: "jpg"),
caption: [
Schermata di un software WMS tradizionale (fonte: #link("https://www.seniorsoftware.ro/en/wms/")[seniorsoftware.ro])
],
) <wms-tradizionale>
Il vantaggio principale di WMS3, rispetto ai tradizionali gestionali di magazzino, è la visualizzazione 3D del magazzino e del suo contenuto. Questa funzionalità rappresenta un miglioramento significativo di usabilità rispetto ai WMS tradizionali. La visualizzazione 3D permette agli utenti di:
- avere una migliore comprensione dello stato del magazzino;
- disporre le operazioni logistiche con maggiore cognizione.
== Panoramica del prodotto
=== Interazioni
Di seguito sono forniti maggiori dettagli riguardo le modalità con cui utenti e altri software possano interagire con WMS3.
// Qui ci starebbe un bel diagramma...
==== Interfacce utente
WMS3 è una _web application_ acceduta e operata tramite browser. L'interfaccia utente (UI) è _web-based_ e _responsive_.
Lo scenario di interazione primario avviene tramite mouse e tastiera; tuttavia, è prevista l'operabilità anche tramite touchscreen. Sarà possibile operare da dispositivi mobili quali tablet e smartphone.
Le funzionalità esposte all'utente variano in base all'ampiezza della _viewport_ del dispositivo in uso. L'insieme completo di funzionalità dovrà essere offerto almeno su computer tramite mouse e tastiera.
==== Interfacce hardware
Il prodotto è acceduto tramite browser. Ne è prevista l'esecuzione sui seguenti dispositivi:
- computer, tramite mouse e tastiera;
- dispositivi mobili touchscreen (es. tablet) in dotazione agli addetti di magazzino.
Il browser e il dispositivo devono essere compatibili con lo standard WebGL.
Il prodotto non prevede elementi hardware propri o interfacce con elementi hardware di terze parti.
==== Interfacce software
WMS3 si interfaccia, in sola lettura, con un database SQL al fine di:
- importare i dati necessari alla costruzione della vista 3D;
- ottenere lo stato interno del magazzino e le informazioni sulla merce contenuta al suo interno.
È previsto che lo schema ER del database venga fornito dal Gruppo al Proponente come artefatto.
==== Interfacce di comunicazione
Per la comunicazione tra le sue componenti, con l'utente e con servizi esterni, WMS3 utilizza HTTP.
==== Vincoli di memoria
Non sono definiti vincoli o limiti sulle memorie primaria e secondaria.
Il Capitolato non prevede che WMS3 offra la persistenza dei dati.
==== Requisiti di adattamento al contesto
WMS3 per essere eseguito richiede:
- un *browser* che supporti WebGL 2.0 (per le specifiche riguardanti i vari browser compatibili consultare la sezione @vincoli);
- un server *Node.js* versione 20.11.0 (latest LTS) o superiore;
- un database relazionale SQL che si interfacci con le API fornite dal gruppo (il gruppo utilizza *PostgreSQL* versione 16.2);
- *Docker Compose* versione 2.23.3 o superiore;
- *Docker* versione 24.0.7 o superiore;
Il gruppo ha deciso di utilizzare la tecnologia Docker per permettere una maggiore portabilità e facilitare il deploy. La gestione simultanea dei container avviene mediante Docker Compose.
Le specifiche sui browser sono imposte dall'utilizzo da parte del gruppo di *Three.js* per implementare l'ambiente 3D.
==== Interfacce a servizi
WMS3 dovrà inviare messaggi ad un servizio esterno per comunicare gli ordini di movimentazione richiesti dall'utente. Dovrà inoltre ricevere e gestire messaggi che comunicano l'esito dell'ordine di movimentazione richiesto.
WMS3 si integra con un sistema esterno per l'immissione degli ordini di movimentazione tramite API RESTful, ma non lo comprende nel proprio ambito. Tale API esterna è incaricata di stabilire se una richiesta di movimentazione inserita tramite WMS3 sia lecita e, quindi, valida per l'inserimento a sistema. I parametri su cui si basa sono recuperati autonomamente dalle fonti dati opportune.
Qualora una richiesta di movimentazione non fosse ritenuta valida, la richiesta di movimentazione è da ritenersi annullata.
WMS3 simulerà il comportamento di tale API con un algoritmo che accetti o rifiuti le richieste di movimentazione in maniera pseudocasuale.
=== Descrizione degli oggetti di dominio
Questo paragrafo fornisce una descrizione dettagliata degli oggetti di dominio, già in parte descritti nel #glo.
==== Ambiente
Di planimetria rettangolare oppure personalizzata (basata su un file SVG caricato durante la configurazione), rappresenta lo spazio interno del magazzino su cui opera l'addetto.
Per agevolare il collocamento delle zone, l'ambiente può essere dotato di una griglia di aggancio posta sulla superficie dell'ambiente. La griglia avrà passo regolabile dall'utente.
Le proprietà sono descritte nella @props-ambiente.
#figure(
table(
columns: 2,
[*Proprietà*], [*Descrizione*],
[Lunghezza], [$>0$ \[m\]],
[Larghezza], [$>0$ \[m\]\ Per planimetrie ricavate da SVG, la larghezza viene calcolata moltiplicando la lunghezza per il rapporto d'aspetto del file SVG.],
),
caption: "Proprietà dell'ambiente"
) <props-ambiente>
==== Zona
Porzione dell'ambiente atta a contenere uno o più bin, organizzati su livelli e colonne. Le proprietà di ciascuna zona sono descritte nella @props-zona.
#figure(
table(
columns: 2,
[*Proprietà*], [*Descrizione*],
[ID], [Identificatore numerico univoco.],
[Lunghezza], [$>0$ \[m\]],
[Larghezza], [$>0$ \[m\]\ Non inferiore alla somma delle larghezze delle colonne.],
[Altezza], [$>0$ \[m\]\ Non inferiore alla somma delle altezze dei livelli.],
[Numero di colonne], [$>=1$],
[Numero di livelli], [$>=1$],
),
caption: "Proprietà di una zona"
) <props-zona>
Le colonne di una stessa zona possono avere larghezze differenti. Ciascuna zona contiene almeno una colonna. Le colonne di una stessa zona sono numerate in modo incrementale.
#figure(
table(
columns: (10em, 10em),
[*Proprietà*], [*Descrizione*],
[ID], [Identificatore alfabetico univoco.],
[Larghezza], [$>0$ \[m\]],
),
caption: "Proprietà di una colonna di una zona"
) <props-colonna>
I livelli partono da terra e sono anche detti "ripiani". Sono numerati dal basso verso l'alto in modo incrementale, a partire da 0. I livelli di una stessa zona possono avere altezze differenti. Ciascuna zona contiene almeno un livello.
#figure(
table(
columns: (10em, 10em),
[*Proprietà*], [*Descrizione*],
[ID], [Identificatore numerico univoco.],
[Altezza], [$>0$ \[m\]],
),
caption: "Proprietà di un livello di una zona"
) <props-livello>
Una rappresentazione esemplificativa del modello di zona adottato per questo progetto è in @schema-zona.
#figure(
image("./imgs/zona.svg", width: 70%),
caption: "Rappresentazione schematica di una zona con tre livelli e tre colonne. In giallo è evidenziato uno dei bin."
) <schema-zona>
Una zona con un solo livello è anche detta "*area a terra*". Modella una zona del magazzino atta a conservare un prodotto per un periodo di tempo tipicamente limitato. Solitamente si tratta di zone di carico/scarico.
Una zona con più di un livello è anche detta "*scaffale*".
==== Bin
Posizione di una zona atta ad accogliere fino ad un prodotto. Individuata dall'intersezione di livelli e colonne.
==== Prodotto
Elemento ospitabile in un bin. Non ci sono richieste specifiche sulle proprietà di un prodotto.
=== Funzionalità del prodotto
Le componenti della visualizzazione 3D godono delle seguenti caratteristiche:
- *Ambiente*:
- dimensioni e planimetria personalizzabili;
- caratterizzato da una griglia (o _grid_) a terra che permette all'utente di collocare con _snapping_ le zone;
- le dimensioni e la finezza della _grid_ possono essere regolate dall'utente;
- navigabile tramite diverse periferiche (frecce direzionali, _mouse_, _touchscreen_ del dispositivo) e in diversi modi (_pan_ sui tre assi, _zoom-in_, _zoom-out_, rotazione).
- *Zona*:
- operazioni CRUD sulle zone;
- operazione di spostamento;
- personalizzazione delle proprietà in fase di creazione;
- ispezione per ottenere informazioni sulla zona e sul suo contenuto;
- ricercabili per ID.
- *Bin*:
- ispezione per ottenere informazioni sul bin e sul suo contenuto.
- *Prodotto*:
- se ne può richiedere lo spostamento (movimentazione) verso un altro bin;
- ispezione per ottenere informazioni;
- ricercabili per ID, nome o categoria.
=== Caratteristiche degli utenti
L'utente tipico di WMS3 è un supervisore di magazzino. Ci si aspetta che la maggior parte degli accessi a WMS3 avvengano da ufficio, tramite un computer desktop dotato di mouse e tastiera; tuttavia, non si può escludere che l'utente possa accedere a WMS3 tramite dispositivo mobile.
L'utente tipico è avvezzo all'uso del computer e dei dispositivi mobili. Conosce il dominio applicativo e ha già dimestichezza con altri strumenti di gestione di magazzino.
=== Limitazioni
Non sono noti requisiti limitanti la capacità dell'organizzazione di realizzare il progetto WMS3, come ad esempio:
- politiche interne, regolamenti, leggi statali;
- limiti hardware;
- limiti imposti dai servizi esterni;
- limiti imposti dai requisiti di qualità;
- considerazioni sulla sicurezza dei dati;
- considerazioni sulla sicurezza dell'utente e di tutti coloro coinvolti, direttamente o indirettamente, dal ciclo di vita di WMS3.
=== Ipotesi e dipendenze
+ Disponibilità di un database SQL popolato;
+ Disponibilità di un browser compatibile con WebGL;
+ Disponibilità di un sistema proprietario per:
+ notificare la richiesta di spostamento di un prodotto all'interno del magazzino al personale designato;
+ ricevere il responso sulla liceità dell'operazione richiesta al punto precedente.
== Principi di redazione
Questo documento è redatto in modo incrementale, così da risultare sempre conforme agli accordi presi tra gruppo e Proponente durante lo sviluppo del progetto. Vengono inoltre adottati i seguenti criteri di qualità:
+ *Correttezza*: ogni caso d'uso e requisito riportato corrisponde a ciò che è richiesto dal Proponente;
+ *Non ambiguità*: ogni parte del documento, caso d'uso e requisito deve essere descritto in modo tale che ne esista una sola interpretazione, e che questa sia facilmente comprensibile da tutte le parti coinvolte nel progetto. A questo scopo, il gruppo _Error\_418_ mette a disposizione un _*Glossario*_ nel quale sono definiti i termini propri del dominio di progetto. Ogni ricorrenza di tali termini nei documenti è segnalata dalla lettera _g_ al pedice;
+ *Completezza*: il documento contiene tutti i requisiti necessari allo sviluppo del progetto, classificandoli per categorie di importanza, e comprende anche la descrizione di tutti i possibili scenari del prodotto;
+ *Coerenza*: ciò che è scritto nel documento non deve andare in conflitto con il contenuto di altri documenti o del documento stesso. Ogni caso d'uso o requisito deve esprimere un concetto diverso dagli altri;
+ *Verificabilità*: deve essere possibile controllare la presenza di ogni requisito nel prodotto finale tramite un procedimento misurabile. La verificabilità è un parametro fortemente influenzato dall'ambiguità: più un requisito è ambiguo, meno sarà verificabile;
+ *Modificabilità*: deve essere definito un modello per la stesura dei singoli casi d'uso e requisiti, così che la loro modifica possa avvenire nel modo più efficiente possibile;
+ *Tracciabilità*: per ogni requisito ne è indicato il riferimento (o fonte), in modo da semplificare il processo di verifica della completezza e correttezza.
#pagebreak()
= Use Case
== Introduzione
In questa sezione sono presentati i casi d'uso e i relativi diagrammi relativi a WMS3. I casi d'uso sono stati definiti a seguito dell'analisi del dominio di applicazione e delle funzionalità richieste dal Proponente, durante riunioni interne ed esterne. Le modalità di definizione sono descritte in #ndp_v, alle sezioni _Processo di analisi della missione_ e _Processo di definizione di bisogni e requisiti degli stakeholder_.
I casi d'uso sono organizzati secondo il dominio di appartenenza:
- *Ambiente 3D* (@uc-ambiente): configurazione e modifica dell'ambiente 3D;
- *Zone e Bin* (@uc-zone): operazioni CRUD sulle zone e gestione dei bin;
- *Prodotti* (@uc-prodotti): gestione dei prodotti e della loro movimentazione.
// Utilities for UC printing
#let printUseCaseInfo(title, ..items) = {
text(title, weight: "bold")
text(": ")
if items.pos().len() > 1 or title in ("Precondizioni", "Postcondizioni", "Inclusioni", "Estensioni", "Generalizzazioni", "Generalizzazione di") {
linebreak()
for item in items.pos() {
if item == items.pos().at(items.pos().len() - 1) [+ #item\.]
else [+ #item\;]
}
}
else {
text(items.pos().join("") + ".")
linebreak()
}
}
#let requirements = json("requirements.json");
#let derivedRequirements(reference) = {
let subset = ()
for key in requirements.keys() {
for req in requirements.at(key) {
if lower(req.source) == ("uc–" + reference) {
subset.push(req.id)
}
}
}
if subset.len() > 0 {
return printUseCaseInfo("Requisiti derivati", subset.join(", "))
}
}
// INIZIO UC
#let setUCHeadingCounterTo(value) = {
let i = 1
while i < value {
counter(heading).step(level: 3)
i+=1
}
}
#set par(first-line-indent: 0pt)
#show heading.where(level: 3): it => {v(3em, weak: true); it}
#show heading.where(level: 4): it => {v(3em, weak: true); it}
#show heading.where(level: 5): it => {v(3em, weak: true); it}
#show heading.where(level: 6): it => {v(3em, weak: true); it}
#show heading.where(level: 7): it => {v(3em, weak: true); it}
#show heading.where(level: 8): it => {v(3em, weak: true); it}
== Ambiente 3D <uc-ambiente>
#set heading(numbering: (..nums) => {
let values = nums.pos().slice(2);
return "UC--" + values.map(str).join(".");
}, supplement: "Caso d'uso")
=== Configurazione ambiente 3D <uc1>
#figure(
image("./imgs/UC1.svg"),
caption: "Diagramma UC--1"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha configurato l'ambiente 3D",
"L'utente dispone di una visualizzazione 3D del magazzino"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona la modalità di configurazione di un ambiente 3D tra le opzioni disponibili"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero configurare un ambiente 3D che rappresenti un magazzino"
)
#printUseCaseInfo(
"Generalizzazioni",
[Configurazione ambiente 3D con planimetria rettangolare (@uc1.1)],
[Configurazione ambiente 3D con planimetria definita da file SVG (@uc1.2)]
)
#derivedRequirements("1")
==== Configurazione ambiente 3D con planimetria rettangolare <uc1.1>
#figure(
image("./imgs/UC1.1.svg"),
caption: "Diagramma UC--1.1"
)
#printUseCaseInfo(
"Generalizzazione di",
[Configurazione ambiente 3D (@uc1)]
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente sta configurando l'ambiente 3D"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha configurato un ambiente 3D con planimetria rettangolare"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona la modalità di configurazione di un ambiente 3D con planimetria rettangolare"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero configurare un ambiente 3D che rappresenti un magazzino con planimetria rettangolare"
)
#derivedRequirements("1.1")
===== Definizione della larghezza ambiente 3D <uc1.1.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha selezionato la configurazione di un ambiente 3D con planimetria rettangolare"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha definito la larghezza dell'ambiente 3D con planimetria rettangolare"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce un valore della larghezza dell'ambiente 3D con planimetria rettangolare"
)
#printUseCaseInfo(
"Scenari alternativi",
"L'utente inserisce un valore minore o uguale a zero"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero definire la larghezza dell'ambiente 3D che rappresenti un magazzino con planimetria rettangolare"
)
#printUseCaseInfo(
"Estensioni",
[Visualizzazione errore larghezza non positiva (@uc1.1.1.1)]
)
#derivedRequirements("1.1.1")
====== Visualizzazione errore larghezza non positiva <uc1.1.1.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha selezionato la configurazione di un ambiente 3D con planimetria rettangolare"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza un errore relativo alla larghezza non positiva"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce un valore della larghezza dell'ambiente 3D con planimetria rettangolare minore o uguale a zero"
)
#derivedRequirements("1.1.1.1")
===== Definizione della lunghezza ambiente 3D <uc1.1.2>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha selezionato la configurazione di un ambiente 3D con planimetria rettangolare"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha definito la lunghezza dell'ambiente 3D con planimetria rettangolare"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce un valore della lunghezza dell'ambiente 3D con planimetria rettangolare"
)
#printUseCaseInfo(
"Scenari alternativi",
"L'utente inserisce un valore minore o uguale a zero"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero definire la lunghezza dell'ambiente 3D che rappresenti un magazzino con planimetria rettangolare"
)
#printUseCaseInfo(
"Estensioni",
[Visualizzazione errore lunghezza non positiva (@uc1.1.2.1)]
)
#derivedRequirements("1.1.2")
====== Visualizzazione errore lunghezza non positiva <uc1.1.2.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha selezionato la configurazione di un ambiente 3D con planimetria rettangolare"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza un errore relativo alla lunghezza non positiva"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce un valore della lunghezza dell'ambiente 3D con planimetria rettangolare minore o uguale a zero"
)
#derivedRequirements("1.1.2.1")
==== Configurazione ambiente 3D con planimetria definita da file SVG <uc1.2>
#figure(
image("./imgs/UC1.2.svg"),
caption: "Diagramma UC--1.2"
)
#printUseCaseInfo(
"Generalizzazione di",
[Configurazione ambiente 3D (@uc1)]
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente sta configurando l'ambiente 3D"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha configurato un ambiente 3D con planimetria definita a partire da file SVG"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona la modalità di configurazione di un ambiente 3D con planimetria definita da file SVG"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero configurare un ambiente 3D con planimetria definita a partire da un file SVG"
)
#derivedRequirements("1.2")
===== Caricamento file SVG <uc1.2.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha selezionato la configurazione di un ambiente 3D con planimetria definita da file SVG"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha caricato correttamente un file SVG valido da utilizzare come planimetria dell'ambiente 3D"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona un file SVG da caricare"
)
#printUseCaseInfo(
"Scenari alternativi",
"L'utente seleziona un file SVG vuoto",
"L'utente seleziona un file non valido al fine della creazione dell'ambiente 3D",
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero caricare un file SVG da utilizzare come planimetria dell'ambiente 3D"
)
#printUseCaseInfo(
"Estensioni",
[Visualizzazione errore file vuoto (@uc1.2.1.1)],
[Visualizzazione errore file non valido (@uc1.2.1.2)]
)
#derivedRequirements("1.2.1")
====== Visualizzazione errore file vuoto <uc1.2.1.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha selezionato la configurazione di un ambiente 3D con planimetria definita da file SVG"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza un errore relativo al caricamento di un file vuoto"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona un file SVG da caricare",
[Nel file SVG caricato non è presente alcun elemento grafico (come `path`, `rect`, `circle`, `ellipse`, `line`, `polyline`, `polygon`, `text`, `g`)]
)
#derivedRequirements("1.2.1.1")
====== Visualizzazione errore file non valido <uc1.2.1.2>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha selezionato la configurazione di un ambiente 3D con planimetria definita da file SVG"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza un errore relativo al caricamento di un file non valido"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona un file non valido (privo della corretta sintassi XML) da caricare"
)
#derivedRequirements("1.2.1.2")
===== Definizione del lato maggiore del magazzino <uc1.2.2>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha selezionato la configurazione di un ambiente 3D con planimetria definita da file SVG"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha definito il lato maggiore dell'ambiente 3D con planimetria definita da file SVG",
"Il sistema ha calcolato il valore del lato minore dell'ambiente 3D con planimetria definita da file SVG a partire dagli attributi del file caricato"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce un valore del lato maggiore dell'ambiente 3D con planimetria definita da file SVG"
)
#printUseCaseInfo(
"Scenari alternativi",
"L'utente inserisce un valore minore o uguale a zero"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero definire il lato maggiore dell'ambiente 3D con planimetria definita da file SVG"
)
#printUseCaseInfo(
"Estensioni",
[Visualizzazione errore lato non positivo (@uc1.2.2.1)]
)
#derivedRequirements("1.2.2")
====== Visualizzazione errore lato non positivo <uc1.2.2.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha selezionato la configurazione di un ambiente 3D con planimetria definita da file SVG"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce un valore del lato maggiore dell'ambiente 3D con planimetria definita da file SVG pari o minore di zero"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza un errore relativo al lato maggiore non positivo"
)
#derivedRequirements("1.2.2.1")
=== Modifica ambiente 3D <uc2>
#figure(
image("./imgs/UC2.svg"),
caption: "Diagramma UC--2"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha configurato un ambiente 3D durante la sessione corrente"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha modificato la configurazione dell'ambiente 3D"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente modifica l'ambiente 3D attualmente configurato"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero modificare un ambiente 3D già configurato, espandendo o riducendo la sua superficie"
)
#derivedRequirements("2")
==== Definizione larghezza <uc2.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha configurato un ambiente 3D durante la sessione corrente",
"L'utente sta riconfigurando l'ambiente 3D"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha ridefinito la larghezza dell'ambiente 3D"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce un valore della larghezza dell'ambiente 3D"
)
#printUseCaseInfo(
"Scenari alternativi",
"L'utente inserisce un valore minore o uguale a zero",
"L'utente inserisce un valore inferiore a quello iniziale"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero ridefinire la larghezza dell'ambiente 3D a seguito della sua configurazione iniziale"
)
#printUseCaseInfo(
"Estensioni",
[Visualizzazione errore larghezza non positiva (@uc2.1.1)],
[Errore dimensione inferiore a quella iniziale (@uc2.3)]
)
#derivedRequirements("2.1")
===== Visualizzazione errore larghezza non positiva <uc2.1.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha configurato un ambiente 3D durante la sessione corrente",
"L'utente sta riconfigurando l'ambiente 3D"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza un errore relativo alla larghezza non positiva"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce un valore della larghezza dell'ambiente 3D pari o minore di zero"
)
#derivedRequirements("2.1.1")
==== Definizione lunghezza <uc2.2>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha configurato un ambiente 3D durante la sessione corrente",
"L'utente sta riconfigurando l'ambiente 3D"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha ridefinito la lunghezza dell'ambiente 3D"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce un valore della lunghezza dell'ambiente 3D"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero ridefinire la lunghezza dell'ambiente 3D a seguito della sua configurazione iniziale"
)
#printUseCaseInfo(
"Estensioni",
[Visualizzazione errore lunghezza non positiva (@uc2.2.1)],
[Errore dimensione inferiore a quella iniziale (@uc2.3)]
)
#derivedRequirements("2.2")
===== Visualizzazione errore lunghezza non positiva <uc2.2.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha configurato un ambiente 3D durante la sessione corrente",
"L'utente sta riconfigurando l'ambiente 3D"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza un errore relativo alla lunghezza non positiva"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce un valore della lunghezza dell'ambiente 3D pari o minore di zero"
)
#derivedRequirements("2.2.1")
==== Errore dimensione inferiore a quella iniziale <uc2.3>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha configurato un ambiente 3D con planimetria definita da file SVG",
"L'utente sta riconfigurando l'ambiente 3D"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza un errore relativo alla dimensione inserita inferiore al rispettivo valore indicato durante la configurazione iniziale dell'ambiente 3D"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce un valore di dimensione (lunghezza o larghezza) inferiore a quella iniziale"
)
#derivedRequirements("2.3")
=== Definizione passo griglia di aggancio <uc3>
#figure(
image("./imgs/UC3.svg", width: 60%),
caption: "Diagramma UC--3"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha creato un ambiente 3D"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha definito il passo della griglia di aggancio, ovvero un numero non negativo espresso in metri"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona un valore del passo della griglia di aggancio"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero definire il passo della griglia di aggancio per poter disporre le zone in modo ordinato. Il passo è un numero non negativo espresso in metri"
)
#derivedRequirements("3")
=== Importazione delle zone da database <uc4>
#figure(
image("./imgs/UC4.svg"),
caption: "Diagramma UC--4"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha impostato un ambiente 3D"
)
#printUseCaseInfo(
"Postcondizioni",
"I dati relativi alle zone sono stati importati correttamente dal database",
"Le zone importate sono state collocate nell'ambiente 3D"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona l'importazione delle zone dal database"
)
#printUseCaseInfo(
"Scenari alternativi",
"L'importazione dal database fallisce"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero importare le zone dal database per poterle visualizzare nell'ambiente 3D"
)
#printUseCaseInfo(
"Inclusioni",
[Importazione dei bin da database (@uc4.1)]
)
#printUseCaseInfo(
"Estensioni",
[Visualizzazione errore importazione dati da database (@uc6)]
)
#derivedRequirements("4")
==== Importazione dei bin da database <uc4.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha impostato un ambiente 3D",
"L'utente ha importato le zone dal database"
)
#printUseCaseInfo(
"Postcondizioni",
"I dati relativi ai bin sono stati importati correttamente dal database"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona l'importazione dei bin dal database"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero importare i bin dal database per poterli visualizzare nell'ambiente 3D all'interno delle zone importate"
)
#derivedRequirements("4.1")
=== Importazione dei prodotti da database <uc5>
#figure(
image("./imgs/UC5.svg", width: 90%),
caption: "Diagramma UC--5"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha impostato un ambiente 3D"
)
#printUseCaseInfo(
"Postcondizioni",
"I dati relativi ai prodotti sono stati importati correttamente dal database"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona l'importazione dei prodotti dal database"
)
#printUseCaseInfo(
"Scenari alternativi",
"L'importazione dal database fallisce"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero importare i prodotti dal database per poterli visualizzare nell'ambiente 3D"
)
#printUseCaseInfo(
"Estensioni",
[Visualizzazione errore importazione dati da database (@uc6)]
)
#derivedRequirements("5")
=== Visualizzazione errore importazione dati da database <uc6>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha impostato un ambiente 3D",
"L'utente ha richiesto l'importazione dei dati dal database"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza un errore relativo all'importazione dei dati dal database"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona l'importazione dei dati dal database ma l'importazione fallisce"
)
#derivedRequirements("6")
=== Rotazione del POV <uc7>
#figure(
image("./imgs/UC7.svg", width: 60%),
caption: "Diagramma UC--7"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha creato un ambiente 3D",
"L'utente interagisce con il sistema per ruotare il proprio punto di vista attorno all'asse longitudinale"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha ruotato il punto di vista lungo l'asse longitudinale"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente ruota il punto di vista tramite mouse, tastiera o touchscreen"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero ruotare il punto di vista attorno all'asse longitudinale per poter visualizzare l'ambiente 3D da diverse angolazioni"
)
#derivedRequirements("7")
=== Panning del POV <uc8>
#figure(
image("./imgs/UC8.svg", width: 60%),
caption: "Diagramma UC--8"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha creato un ambiente 3D",
"L'utente interagisce con il sistema per spostare il proprio punto di vista lungo l'asse orizzontale"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha spostato il punto di vista lungo l'asse orizzontale"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente sposta il punto di vista tramite mouse, tastiera o touchscreen"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero spostare orizzontalmente il punto di vista per poter visualizzare l'ambiente 3D da diverse posizioni"
)
#derivedRequirements("8")
=== Zoom-in sull'ambiente 3D <uc9>
#figure(
image("./imgs/UC9.svg", width: 60%),
caption: "Diagramma UC--9"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha creato un ambiente 3D",
"L'utente interagisce con il sistema per effettuare lo zoom-in"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha ristretto il proprio campo visivo sull'ambiente 3D",
"L'utente ha avvicinato il proprio punto di vista all'ambiente 3D"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente effettua lo zoom-in tramite mouse, tastiera o touchscreen"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero effettuare lo zoom-in per poter visualizzare l'ambiente 3D da diverse distanze"
)
#derivedRequirements("9")
=== Zoom-out sull'ambiente 3D <uc10>
#figure(
image("./imgs/UC10.svg", width: 60%),
caption: "Diagramma UC--10"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha creato un ambiente 3D",
"L'utente interagisce con il sistema per effettuare lo zoom-out"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha allargato il proprio campo visivo sull'ambiente 3D",
"L'utente ha allontanato il proprio punto di vista sull'ambiente 3D",
)
#printUseCaseInfo(
"Scenario principale",
"L'utente effettua lo zoom-out tramite mouse, tastiera o touchscreen"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero effettuare lo zoom-out per poter visualizzare l'ambiente 3D da diverse distanze"
)
#derivedRequirements("10")
=== Reimpostazione ambiente 3D <uc11>
#figure(
image("./imgs/UC11.svg"),
caption: "Diagramma UC--11"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha impostato un ambiente 3D",
)
#printUseCaseInfo(
"Postcondizioni",
"La configurazione dell'ambiente 3D è stata reimpostata"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente richiede la reimpostazione dell'ambiente 3D"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero reimpostare un ambiente 3D già configurato, compresi i dati eventualmente importati da database e quelli immessi manualmente, per poter ricominciare da zero con impostazioni diverse"
)
#printUseCaseInfo(
"Inclusioni",
[Reset movimentazioni (@uc11.1)],
[Reset modifiche alle zone (@uc11.2)],
[Reset planimetria (@uc11.3)],
[Rimozione dati importati (@uc11.4)]
)
#derivedRequirements("11")
==== Reset movimentazioni <uc11.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha impostato un ambiente 3D",
)
#printUseCaseInfo(
"Postcondizioni",
"La lista delle movimentazioni è stata azzerata",
)
#printUseCaseInfo(
"Scenario principale",
"L'utente richiede la reimpostazione dell'ambiente 3D"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero reimpostare le movimentazioni per poter tornare allo stato iniziale"
)
#derivedRequirements("11.1")
==== Reset modifiche alle zone <uc11.2>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha impostato un ambiente 3D",
)
#printUseCaseInfo(
"Postcondizioni",
"Tutte le modifiche alle zone (incluse aggiunte e cancellazioni) sono state annullate"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente richiede la reimpostazione dell'ambiente 3D"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero reimpostare le modifiche alle zone per poter ricominciare da zero la configurazione dell'ambiente 3D"
)
#derivedRequirements("11.2")
==== Reset planimetria <uc11.3>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha impostato un ambiente 3D",
)
#printUseCaseInfo(
"Postcondizioni",
"La configurazione della planimetria è stata reimpostata"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente richiede la reimpostazione dell'ambiente 3D"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero reimpostare la planimetria per poter ricominciare da zero la configurazione dell'ambiente 3D"
)
#derivedRequirements("11.3")
==== Rimozione dati importati <uc11.4>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha impostato un ambiente 3D",
)
#printUseCaseInfo(
"Postcondizioni",
"I dati importati da database sono stati rimossi"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente richiede la reimpostazione dell'ambiente 3D"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero rimuovere i dati importati da database per poter ricominciare da zero la configurazione dell'ambiente 3D"
)
#derivedRequirements("11.4")
#pagebreak()
#set heading(numbering: "1.1", supplement: "Sezione")
== Zone e Bin <uc-zone>
#set heading(numbering: (..nums) => {
let values = nums.pos().slice(2);
return "UC--" + values.map(str).join(".");
}, supplement: "Caso d'uso")
#setUCHeadingCounterTo(12)
=== Creazione zona <uc12>
#figure(
image("./imgs/UC12.svg", width: 120%),
caption: "Diagramma UC--12"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha creato un ambiente 3D"
)
#printUseCaseInfo(
"Postcondizioni",
"La zona è stata aggiunta all'ambiente 3D"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente configura una nuova zona da creare",
"L'utente colloca la zona in una posizione valida nell'ambiente 3D"
)
#printUseCaseInfo(
"Inclusioni",
[Definizione ID zona (@uc12.1)],
[Definizione lunghezza zona (@uc12.2)],
[Definizione orientamento zona (@uc12.3)],
[Definizione colonne zona (@uc12.4)],
[Definizione livelli zona (@uc12.5)],
[Collocamento della zona nell'ambiente 3D (@uc16)]
)
#derivedRequirements("12")
==== Definizione ID zona <uc12.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente sta configurando una nuova zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha definito l'ID della zona"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce un valore dell'ID della zona"
)
#printUseCaseInfo(
"Scenari alternativi",
"L'utente inserisce un valore già utilizzato per un'altra zona"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero definire l'ID di una zona per poterla identificare in modo univoco"
)
#printUseCaseInfo(
"Estensioni",
[Visualizzazione errore ID zona già in uso (@uc12.1.1)]
)
#derivedRequirements("12.1")
===== Visualizzazione errore ID zona già in uso <uc12.1.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente sta configurando una nuova zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza un errore relativo all'ID della zona già in uso"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce un valore dell'ID della zona già associato ad un'altra zona"
)
#derivedRequirements("12.1.1")
==== Definizione lunghezza zona <uc12.2>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente sta configurando una nuova zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha definito la lunghezza della zona"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce un valore della lunghezza della zona"
)
#printUseCaseInfo(
"Scenari alternativi",
"L'utente inserisce un valore minore o uguale a zero"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero definire la lunghezza di una zona per poterla collocare nell'ambiente 3D"
)
#printUseCaseInfo(
"Estensioni",
[Visualizzazione errore lunghezza non positiva (@uc12.2.1)]
)
#derivedRequirements("12.2")
===== Visualizzazione errore lunghezza non positiva <uc12.2.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente sta configurando una nuova zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza un errore relativo alla lunghezza non positiva"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce un valore della lunghezza della zona pari o minore di zero"
)
#derivedRequirements("12.2.1")
==== Definizione orientamento zona <uc12.3>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente sta configurando una nuova zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha definito l'orientamento della zona"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona un valore dell'orientamento della zona tra i valori disponibili"
)
#printUseCaseInfo(
"User story associata",
[Come utente, desidero definire l'orientamento di una zona (tra "nord-sud" (`NS`) e "ovest-est" (`WE`)) per poterla collocare nell'ambiente 3D]
)
#derivedRequirements("12.3")
==== Definizione colonne zona <uc12.4>
#figure(
image("./imgs/UC12.4.svg", width: 120%),
caption: "Diagramma UC--12.4"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente sta configurando una nuova zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha definito le proprietà delle colonne della zona"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente definisce le proprietà delle colonne della zona"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero personalizzare le colonne di una zona per poterla rendere il più simile possibile all'ambiente reale"
)
#derivedRequirements("12.4")
===== Definizione numero colonne <uc12.4.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente sta configurando una nuova zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha definito il numero di colonne della zona"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce il numero di colonne della zona"
)
#printUseCaseInfo(
"Scenari alternativi",
"L'utente inserisce un valore minore di 1"
)
#printUseCaseInfo(
"Estensioni",
[Visualizzazione errore numero colonne non conforme (@uc12.4.1.1)]
)
#derivedRequirements("12.4.1")
====== Visualizzazione errore numero colonne non conforme <uc12.4.1.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente sta configurando una nuova zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza un errore relativo al valore immesso non conforme"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce un numero di colonne minore di 1"
)
#derivedRequirements("192.168.3.11")
===== Definizione larghezza colonne <uc12.4.2>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente sta configurando una nuova zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha definito la larghezza delle colonne della zona",
"La larghezza della zona è calcolata come la somma delle larghezze delle singole colonne"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente definisce la larghezza delle colonne della zona secondo una delle modalità disponibili"
)
#printUseCaseInfo(
"Generalizzazioni",
[Definizione larghezza colonne tramite equa distribuzione (@uc12.4.2.1)],
[Definizione larghezza colonne personalizzata (@uc12.4.2.2)]
)
#derivedRequirements("12.4.2")
====== Definizione larghezza colonne tramite equa distribuzione <uc12.4.2.1>
#printUseCaseInfo(
"Generalizzazione di",
[Definizione larghezza colonne (@uc12.4.2)]
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha definito la larghezza delle colonne della zona",
"La larghezza della zona è suddivisa equamente in tante parti quante sono le colonne",
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona la modalità di equa distribuzione della larghezza delle colonne",
)
#printUseCaseInfo(
"Inclusioni",
[Definizione larghezza zona (@uc12.4.2.1.1)]
)
#derivedRequirements("172.16.17.32")
======= Definizione larghezza zona <uc12.4.2.1.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente sta configurando una nuova zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha definito la larghezza della zona"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce un valore della larghezza della zona"
)
#printUseCaseInfo(
"Scenari alternativi",
"L'utente inserisce un valore minore o uguale a zero"
)
#printUseCaseInfo(
"Estensioni",
[Visualizzazione errore larghezza non positiva (@uc12.4.3)]
)
#derivedRequirements("172.16.17.32.1")
====== Definizione larghezza colonne personalizzata <uc12.4.2.2>
#printUseCaseInfo(
"Generalizzazione di",
[Definizione larghezza colonne (@uc12.4.2)]
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha definito la larghezza delle colonne della zona",
"La larghezza della zona è suddivisa in tante parti quante sono le colonne, ciascuna con larghezza personalizzata",
"La larghezza della zona è calcolata come la somma delle larghezze delle singole colonne"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente definisce la larghezza di ciascuna colonna della zona"
)
#printUseCaseInfo(
"Inclusioni",
[Definizione larghezza singola colonna (@uc12.4.2.2.1)]
)
#derivedRequirements("172.16.31.10")
======= Definizione larghezza singola colonna <uc12.4.2.2.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente sta configurando una nuova zona",
"L'utente ha selezionato la modalità di definizione personalizzata della larghezza delle colonne"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha definito la larghezza di una colonna della zona"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce un valore della larghezza di una colonna della zona"
)
#printUseCaseInfo(
"Scenari alternativi",
"L'utente inserisce un valore minore o uguale a zero"
)
#printUseCaseInfo(
"Estensioni",
[Visualizzazione errore larghezza non positiva (@uc12.4.3)]
)
#derivedRequirements("12.4.2.2.1")
===== Visualizzazione errore larghezza non positiva <uc12.4.3>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente sta configurando una nuova zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza un errore relativo alla larghezza non positiva"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce un valore della larghezza minore o uguale a zero"
)
#derivedRequirements("12.4.3")
==== Definizione livelli zona <uc12.5>
#figure(
image("./imgs/UC12.5.svg", width: 80%),
caption: "Diagramma UC--12.5"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente sta configurando una nuova zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha definito le proprietà dei livelli della zona"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente definisce le proprietà dei livelli della zona"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero personalizzare i livelli di una zona per poterla rendere il più simile possibile all'ambiente reale"
)
#derivedRequirements("12.5")
===== Definizione numero livelli <uc12.5.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente sta configurando una nuova zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha definito il numero di livelli della zona"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce il numero di livelli della zona"
)
#printUseCaseInfo(
"Scenari alternativi",
"L'utente inserisce un valore minore o uguale a zero"
)
#printUseCaseInfo(
"Estensioni",
[Visualizzazione errore numero livelli minore o uguale a zero (@uc12.5.1.1)]
)
#derivedRequirements("12.5.1")
====== Visualizzazione errore numero livelli minore o uguale a zero <uc12.5.1.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente sta configurando una nuova zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza un errore relativo al valore immesso minore o uguale a zero"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce un numero di livelli minore o uguale a zero"
)
#derivedRequirements("172.16.17.32")
===== Definizione altezza livelli <uc12.5.2>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente sta configurando una nuova zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha definito l'altezza dei livelli della zona secondo una delle modalità disponibili",
"L'altezza della zona è calcolata come la somma delle altezze dei singoli livelli"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona una modalità di definizione dell'altezza dei livelli della zona tra quelle disponibili"
)
#printUseCaseInfo(
"Generalizzazioni",
[Definizione altezza livelli personalizzata (@uc12.5.2.1)],
)
#derivedRequirements("12.5.2")
====== Definizione altezza livelli personalizzata <uc12.5.2.1>
#printUseCaseInfo(
"Generalizzazione di",
[Definizione altezza livelli (@uc12.5.2)]
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha definito l'altezza dei livelli della zona",
"L'altezza della zona è suddivisa in tante parti quante sono i livelli, ciascuna con altezza personalizzata"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente definisce l'altezza di ciascun livello della zona"
)
#printUseCaseInfo(
"Inclusioni",
[Definizione altezza singolo livello (@uc12.5.2.1.1)]
)
#derivedRequirements("172.16.31.10")
======= Definizione altezza singolo livello <uc12.5.2.1.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente sta configurando una nuova zona",
"L'utente ha selezionato la modalità di definizione personalizzata dell'altezza dei livelli della zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente ha definito l'altezza di un livello della zona"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce un valore dell'altezza di un livello della zona"
)
#printUseCaseInfo(
"Scenari alternativi",
"L'utente inserisce un valore minore o uguale a zero"
)
#derivedRequirements("12.5.2.1.1")
======== Visualizzazione errore altezza non positiva <uc12.5.2.1.1.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente sta configurando una nuova zona",
"L'utente ha selezionato la modalità di definizione personalizzata dell'altezza dei livelli della zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza un errore relativo all'altezza non positiva"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce un valore dell'altezza minore o uguale a zero"
)
#derivedRequirements("12.5.2.1.1.1")
=== Modifica zona <uc13>
#figure(
image("./imgs/UC13.svg", width: 120%),
caption: "Diagramma UC--13"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha creato un ambiente 3D",
"Nell'ambiente 3D è presente almeno una zona"
)
#printUseCaseInfo(
"Postcondizioni",
"La zona è stata modificata"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona la zona da modificare",
"L'utente modifica le proprietà della zona"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero modificare le proprietà di una zona, creata in precedenza o importata da database, per poterla adattare alle mie esigenze"
)
#printUseCaseInfo(
"Inclusioni",
[Definizione lunghezza zona (@uc12.2)],
[Definizione orientamento zona (@uc12.3)],
[Definizione colonne zona (@uc12.4)],
[Definizione livelli zona (@uc12.5)],
[Collocamento della zona nell'ambiente 3D (@uc16)]
)
#printUseCaseInfo(
"Estensioni",
[Rimozione singola colonna (@uc13.1)],
[Rimozione singolo livello (@uc13.2)],
)
#derivedRequirements("13")
==== Rimozione singola colonna <uc13.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha creato un ambiente 3D",
"L'utente sta modificando una zona",
"La zona modificata possiede almeno 2 colonne"
)
#printUseCaseInfo(
"Postcondizioni",
"La colonna selezionata è stata rimossa dalla zona"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona una colonna vuota da rimuovere",
)
#printUseCaseInfo(
"Scenari alternativi",
"L'utente seleziona una colonna con almeno un bin occupato",
"L'utente seleziona una colonna vuota con indice inferiore ad una colonna con almeno un bin occupato"
)
#printUseCaseInfo(
"Estensioni",
[Visualizzazione errore operazione impossibile perché insiste su bin occupato (@uc13.3)]
)
#derivedRequirements("13.1")
==== Rimozione singolo livello <uc13.2>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha creato un ambiente 3D",
"L'utente sta modificando una zona",
"La zona modificata possiede almeno 2 livelli"
)
#printUseCaseInfo(
"Postcondizioni",
"Il livello selezionato è stato rimosso dalla zona"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona un livello vuoto da rimuovere",
)
#printUseCaseInfo(
"Scenari alternativi",
"L'utente seleziona un livello con almeno un bin occupato",
"L'utente seleziona un livello vuoto con indice inferiore ad un livello con almeno un bin occupato"
)
#printUseCaseInfo(
"Estensioni",
[Visualizzazione errore operazione impossibile perché insiste su bin occupato (@uc13.3)]
)
#derivedRequirements("13.2")
==== Visualizzazione errore operazione impossibile perché insiste su bin occupato <uc13.3>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha creato un ambiente 3D",
"L'utente sta modificando una zona",
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza un errore relativo all'impossibilità di rimuovere la colonna o il livello selezionato"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente richiede la rimozione di una colonna o di un livello con almeno un bin occupato"
)
#derivedRequirements("13.3")
=== Eliminazione zona <uc14>
#figure(
image("./imgs/UC14.svg", width: 60%),
caption: "Diagramma UC--14"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha creato un ambiente 3D",
"Nell'ambiente 3D è presente almeno una zona"
)
#printUseCaseInfo(
"Postcondizioni",
"La zona è stata eliminata dall'ambiente 3D",
"I prodotti collocati nei bin della zona rimossa sono elencati nella lista dei prodotti senza collocazione"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona la zona da eliminare",
"L'utente conferma l'eliminazione della zona"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero eliminare una zona dall'ambiente 3D per fare spazio ad altre zone o semplicemente per rimuoverla"
)
#derivedRequirements("14")
=== Ispezione zona <uc15>
#figure(
image("./imgs/UC15.svg", width: 110%),
caption: "Diagramma UC--15"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha creato un ambiente 3D",
"Nell'ambiente 3D è presente almeno una zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza le informazioni relative alla zona selezionata"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona una zona da ispezionare"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero visualizzare le informazioni associate ad una zona"
)
#printUseCaseInfo(
"Inclusioni",
[Visualizzazione ID zona (@uc15.1)],
[Visualizzazione larghezza zona (@uc15.2)],
[Visualizzazione lunghezza zona (@uc15.3)],
[Visualizzazione altezza zona (@uc15.4)],
[Evidenziazione zona selezionata (@uc15.5)],
[Visualizzazione lista bin inclusi nella zona (@uc15.6)]
)
#derivedRequirements("15")
==== Visualizzazione ID zona <uc15.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha creato un ambiente 3D",
"Nell'ambiente 3D è presente almeno una zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza l'ID della zona selezionata"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona una zona da ispezionare"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero visualizzare l'ID di una zona per poterla identificare in modo univoco"
)
#derivedRequirements("15.1")
==== Visualizzazione larghezza zona <uc15.2>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha creato un ambiente 3D",
"Nell'ambiente 3D è presente almeno una zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza la larghezza della zona selezionata"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona una zona da ispezionare"
)
#derivedRequirements("15.2")
==== Visualizzazione lunghezza zona <uc15.3>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha creato un ambiente 3D",
"Nell'ambiente 3D è presente almeno una zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza la lunghezza della zona selezionata"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona una zona da ispezionare"
)
#derivedRequirements("15.3")
==== Visualizzazione altezza zona <uc15.4>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha creato un ambiente 3D",
"Nell'ambiente 3D è presente almeno una zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza l'altezza della zona selezionata"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona una zona da ispezionare"
)
#derivedRequirements("15.4")
==== Evidenziazione zona selezionata <uc15.5>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha creato un ambiente 3D",
"Nell'ambiente 3D è presente almeno una zona"
)
#printUseCaseInfo(
"Postcondizioni",
"La zona selezionata è evidenziata nell'ambiente 3D"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona una zona da ispezionare"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero che la zona ispezionata venga evidenziata graficamente per poterla individuare a colpo d'occhio nell'ambiente 3D"
)
#derivedRequirements("15.5")
==== Visualizzazione lista bin inclusi nella zona <uc15.6>
#figure(
image("./imgs/UC15.6.svg", width: 90%),
caption: "Diagramma UC--15.6"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha creato un ambiente 3D",
"Nell'ambiente 3D è presente almeno una zona",
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza la lista dei bin inclusi nella zona selezionata"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona una zona da ispezionare"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero visualizzare la lista dei bin inclusi in una zona per poter controllare la disposizione dei prodotti e il tasso di occupazione della zona stessa"
)
#printUseCaseInfo(
"Inclusioni",
[Visualizzazione singolo bin (@uc15.6.1)]
)
#derivedRequirements("15.6")
===== Visualizzazione singolo bin <uc15.6.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente sta ispezionando una zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza le informazioni relative ad un singolo bin presente nella zona selezionata"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente visualizza un elemento della lista delle zone"
)
#printUseCaseInfo(
"Inclusioni",
[Visualizzazione ID bin (@uc15.6.1.1)],
[Visualizzazione stato bin (@uc15.6.1.2)],
)
#derivedRequirements("15.6.1")
====== Visualizzazione ID bin <uc15.6.1.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente sta ispezionando una zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza l'ID del bin selezionato"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente visualizza un elemento della lista dei bin"
)
#derivedRequirements("15.6.1.1")
====== Visualizzazione stato bin <uc15.6.1.2>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente sta ispezionando una zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza lo stato di occupazione del bin selezionato"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente visualizza un elemento della lista dei bin"
)
#derivedRequirements("15.6.1.2")
=== Collocamento della zona nell'ambiente 3D <uc16>
#figure(
image("./imgs/UC16.svg", width: 110%),
caption: "Diagramma UC--16"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha creato un ambiente 3D",
)
#printUseCaseInfo(
"Postcondizioni",
"La zona è stata collocata nell'ambiente 3D",
)
#printUseCaseInfo(
"Scenario principale",
[L'utente seleziona una zona da collocare, tramite creazione (@uc12) o modifica (@uc13)],
"L'utente posiziona la zona nell'ambiente 3D",
"L'utente conferma il collocamento della zona nell'ambiente 3D"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero collocare una zona in una posizione specifica dell'ambiente 3D"
)
#printUseCaseInfo(
"Estensioni",
[Evidenziazione zona non collocabile (@uc16.1)],
)
#derivedRequirements("16")
==== Evidenziazione zona non collocabile <uc16.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha creato un ambiente 3D",
"L'utente ha selezionato una zona da collocare",
)
#printUseCaseInfo(
"Postcondizioni",
[L'utente visualizza un _hint_ grafico relativo all'impossibilità di collocare la zona nella posizione desiderata],
"La zona non viene collocata nell'ambiente 3D"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente tenta di collocare una zona in una posizione non valida"
)
#printUseCaseInfo(
"Generalizzazioni",
[Evidenziazione zona collisa con zone già collocate (@uc16.1.1)],
[Evidenziazione zona non collocabile perché al di fuori del perimetro (@uc16.1.2)],
)
#derivedRequirements("16.1")
===== Evidenziazione zona collisa con zone già collocate <uc16.1.1>
#printUseCaseInfo(
"Generalizzazione di",
[Evidenziazione zona non collocabile (@uc16.1)]
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Scenario principale",
"L'utente tenta di collocare una zona in una posizione già occupata da un'altra zona",
"Le zone si sovrappongono e collidono"
)
#derivedRequirements("16.1.1")
===== Evidenziazione zona non collocabile perché al di fuori del perimetro <uc16.1.2>
#printUseCaseInfo(
"Generalizzazione di",
[Evidenziazione zona non collocabile (@uc16.1)]
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Scenario principale",
"L'utente tenta di collocare una zona al di fuori del perimetro dell'ambiente 3D"
)
#derivedRequirements("16.1.2")
=== Visualizzazione lista zone <uc17>
#figure(
image("./imgs/UC17.svg"),
caption: "Diagramma UC--17"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha creato un ambiente 3D",
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza la lista delle zone presenti nell'ambiente 3D"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente richiede la visualizzazione della lista delle zone"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero visualizzare la lista delle zone presenti nell'ambiente 3D"
)
#printUseCaseInfo(
"Inclusioni",
[Visualizzazione singola zona (@uc17.1)],
)
#derivedRequirements("17")
==== Visualizzazione singola zona <uc17.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha richiesto la visualizzazione della lista delle zone",
"È presente almeno una zona nell'ambiente 3D"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza le informazioni relative ad una singola zona presente in lista"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente visualizza un elemento della lista delle zone"
)
#printUseCaseInfo(
"Inclusioni",
[Visualizzazione ID zona (@uc17.1.1)],
)
#derivedRequirements("17.1")
===== Visualizzazione ID zona <uc17.1.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha richiesto la visualizzazione della lista delle zone",
"È presente almeno una zona nell'ambiente 3D"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza l'ID della zona visualizzata"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente visualizza un elemento della lista delle zone"
)
#derivedRequirements("17.1.1")
=== Ricerca zona <uc18>
#figure(
image("./imgs/UC18.svg", width: 80%),
caption: "Diagramma UC--18"
)
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza i risultati della ricerca filtrati secondo il termine inserito e la modalità scelta"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona la modalità di ricerca tra quelle disponibili",
"L'utente inserisce il termine di ricerca"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero poter ricercare una zona per individuarla velocemente nella lista delle zone"
)
#printUseCaseInfo(
"Generalizzazioni",
[Ricerca per ID zona (@uc18.1)],
)
#derivedRequirements("18")
==== Ricerca per ID zona <uc18.1>
#printUseCaseInfo(
"Generalizzazione di",
[Ricerca prodotti (@uc18)]
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza la lista delle zone filtrata secondo l'ID della zona inserito come termine di ricerca"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce l'ID della zona da cercare"
)
#derivedRequirements("18.1")
=== Ispezione bin <uc19>
#figure(
image("./imgs/UC19.svg"),
caption: "Diagramma UC--19"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha creato un ambiente 3D",
"Nell'ambiente 3D è presente almeno una zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza le informazioni relative al bin selezionato"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona un bin da ispezionare"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero visualizzare le informazioni associate ai bin presenti nell'ambiente 3D"
)
#printUseCaseInfo(
"Inclusioni",
[Visualizzazione ID bin (@uc19.1)],
[Visualizzazione lunghezza (@uc19.2)],
[Visualizzazione larghezza (@uc19.3)],
[Visualizzazione altezza (@uc19.4)],
[Evidenziazione bin selezionato (@uc19.5)],
)
#printUseCaseInfo(
"Estensioni",
[Visualizzazione informazioni prodotto (@uc22)]
)
#derivedRequirements("19")
==== Visualizzazione ID bin <uc19.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha creato un ambiente 3D",
"Nell'ambiente 3D è presente almeno una zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza l'ID del bin selezionato"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona un bin da ispezionare"
)
#derivedRequirements("19.1")
==== Visualizzazione lunghezza bin <uc19.2>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha creato un ambiente 3D",
"Nell'ambiente 3D è presente almeno una zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza la lunghezza del bin selezionato"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona un bin da ispezionare"
)
#derivedRequirements("19.2")
==== Visualizzazione larghezza bin <uc19.3>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha creato un ambiente 3D",
"Nell'ambiente 3D è presente almeno una zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza la larghezza del bin selezionato"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona un bin da ispezionare"
)
#derivedRequirements("19.3")
==== Visualizzazione altezza bin <uc19.4>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha creato un ambiente 3D",
"Nell'ambiente 3D è presente almeno una zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza l'altezza del bin selezionato"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona un bin da ispezionare"
)
#derivedRequirements("19.4")
==== Evidenziazione bin selezionato <uc19.5>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha creato un ambiente 3D",
"Nell'ambiente 3D è presente almeno una zona"
)
#printUseCaseInfo(
"Postcondizioni",
"Il bin selezionato è evidenziato nell'ambiente 3D"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona un bin da ispezionare"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero che il bin ispezionato venga evidenziato graficamente per poterlo individuare a colpo d'occhio nell'ambiente 3D"
)
#derivedRequirements("19.5")
=== Spostamento POV su zona specifica <uc20>
#figure(
image("./imgs/UC20.svg", width: 80%),
caption: "Diagramma UC--20"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha creato un ambiente 3D",
"Nell'ambiente 3D è presente almeno una zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'inquadratura dell'ambiente 3D si sposta sulla zona specificata"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona una zona da ispezionare",
"L'utente richiede lo spostamento del POV così da inquadrare la zona"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero spostare il POV sull'ambiente 3D per poter visualizzare una zona specifica"
)
#derivedRequirements("20")
=== Spostamento POV su bin specifico <uc21>
#figure(
image("./imgs/UC21.svg", width: 80%),
caption: "Diagramma UC--21"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha creato un ambiente 3D",
"Nell'ambiente 3D è presente almeno una zona"
)
#printUseCaseInfo(
"Postcondizioni",
"L'inquadratura dell'ambiente 3D si sposta sul bin specificato"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona un bin da ispezionare",
"L'utente richiede lo spostamento del POV così da inquadrare il bin"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero spostare il POV sull'ambiente 3D per poter visualizzare un bin specifico"
)
#derivedRequirements("21")
#pagebreak()
#set heading(numbering: "1.1", supplement: "Sezione")
== Prodotti <uc-prodotti>
#set heading(numbering: (..nums) => {
let values = nums.pos().slice(2);
return "UC--" + values.map(str).join(".");
}, supplement: "Caso d'uso")
#setUCHeadingCounterTo(22)
=== Visualizzazione informazioni prodotto <uc22>
#figure(
image("./imgs/UC22.1.svg", width: 75%),
caption: "Diagramma UC--22"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha richiesto l'importazione dei prodotti",
"Il sistema ha importato correttamente almeno un prodotto"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza le informazioni relative al prodotto selezionato"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona un prodotto da ispezionare"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero visualizzare le informazioni associate ai prodotti presenti nel magazzino"
)
#printUseCaseInfo(
"Inclusioni",
[Visualizzazione ID prodotto (@uc22.1)],
[Visualizzazione nome prodotto (@uc22.2)],
[Visualizzazione categoria prodotto (@uc22.3)],
[Visualizzazione larghezza prodotto (@uc22.4)],
[Visualizzazione lunghezza prodotto (@uc22.5)],
[Visualizzazione altezza prodotto (@uc22.6)],
[Visualizzazione peso prodotto (@uc22.7)],
)
#derivedRequirements("22")
==== Visualizzazione ID prodotto <uc22.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha selezionato un prodotto da ispezionare"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza l'ID del prodotto selezionato"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona un prodotto da ispezionare"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero visualizzare l'informazione sull'ID di un prodotto"
)
#derivedRequirements("22.1")
==== Visualizzazione nome prodotto <uc22.2>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha selezionato un prodotto da ispezionare"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza il nome del prodotto selezionato"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona un prodotto da ispezionare"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero visualizzare l'informazione sul nome di un prodotto"
)
#derivedRequirements("22.2")
==== Visualizzazione categoria prodotto <uc22.3>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha selezionato un prodotto da ispezionare"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza la categoria del prodotto selezionato"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona un prodotto da ispezionare"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero visualizzare l'informazione sulla categoria di un prodotto"
)
#derivedRequirements("22.3")
==== Visualizzazione larghezza prodotto <uc22.4>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha selezionato un prodotto da ispezionare"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza la larghezza del prodotto selezionato"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona un prodotto da ispezionare"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero visualizzare l'informazione sulla larghezza di un prodotto"
)
#derivedRequirements("22.4")
==== Visualizzazione lunghezza prodotto <uc22.5>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha selezionato un prodotto da ispezionare"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza la lunghezza del prodotto selezionato"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona un prodotto da ispezionare"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero visualizzare l'informazione sulla lunghezza di un prodotto"
)
#derivedRequirements("22.5")
==== Visualizzazione altezza prodotto <uc22.6>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha selezionato un prodotto da ispezionare"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza l'altezza del prodotto selezionato"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona un prodotto da ispezionare"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero visualizzare l'informazione sull'altezza di un prodotto"
)
#derivedRequirements("22.6")
==== Visualizzazione peso prodotto <uc22.7>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha selezionato un prodotto da ispezionare"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza il peso del prodotto selezionato"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona un prodotto da ispezionare"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero visualizzare l'informazione sul peso di un prodotto"
)
#derivedRequirements("22.7")
=== Visualizzazione lista prodotti <uc23>
#figure(
image("./imgs/UC23.svg", width: 115%),
caption: "Diagramma UC--23"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha richiesto l'importazione dei prodotti",
"Il sistema ha importato correttamente almeno un prodotto"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza la lista dei prodotti importati secondo il criterio selezionato"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente richiede la visualizzazione di una delle liste di prodotti tra quelle disponibili"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero visualizzare la lista dei prodotti importati da database e visualizzarne i dettagli"
)
#printUseCaseInfo(
"Generalizzazioni",
[Visualizzazione lista prodotti non collocati (@uc23.1)],
[Visualizzazione lista prodotti collocati (@uc23.2)]
)
#derivedRequirements("23")
==== Visualizzazione lista prodotti non collocati <uc23.1>
#figure(
image("./imgs/UC23.1.1.svg", width: 80%),
caption: "Diagramma UC--23.1"
)
#printUseCaseInfo(
"Generalizzazione di",
[Visualizzazione lista prodotti (@uc23)]
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza la lista dei prodotti non collocati nei bin"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente richiede la visualizzazione della lista dei prodotti non collocati nei bin"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero visualizzare la lista dei prodotti non collocati nei bin delle zone dell'ambiente 3D per poterli collocare"
)
#printUseCaseInfo(
"Inclusioni",
[Visualizzazione singolo prodotto (@uc23.1.1)]
)
#derivedRequirements("23.1")
===== Visualizzazione singolo prodotto <uc23.1.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha richiesto la visualizzazione della lista dei prodotti"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza le informazioni relative ad un singolo prodotto, non collocato nei bin, presente in lista"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente richiede la visualizzazione della lista dei prodotti non collocati nei bin"
)
#printUseCaseInfo(
"Generalizzazioni",
[Visualizzazione singolo prodotto collocato (@uc23.2.1)]
)
#printUseCaseInfo(
"Inclusioni",
[Visualizzazione nome prodotto (@uc23.1.1.1)],
[Visualizzazione ID prodotto (@uc23.1.1.2)],
[Visualizzazione categoria prodotto (@uc23.1.1.3)]
)
#derivedRequirements("23.1.1")
====== Visualizzazione nome prodotto <uc23.1.1.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha richiesto la visualizzazione della lista dei prodotti"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza il nome del prodotto visualizzato"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente visualizza un elemento della lista dei prodotti"
)
#derivedRequirements("23.1.1.1")
====== Visualizzazione ID prodotto <uc23.1.1.2>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha richiesto la visualizzazione della lista dei prodotti"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza l'ID del prodotto visualizzato"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente visualizza un elemento della lista dei prodotti"
)
#derivedRequirements("2192.168.3.11")
====== Visualizzazione categoria prodotto <uc23.1.1.3>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha richiesto la visualizzazione della lista dei prodotti"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza la categoria del prodotto visualizzato"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente visualizza un elemento della lista dei prodotti"
)
#derivedRequirements("23.1.1.3")
==== Visualizzazione lista prodotti collocati <uc23.2>
#figure(
image("./imgs/UC23.2.1.svg", width: 80%),
caption: "Diagramma UC--23.2.1"
)
#printUseCaseInfo(
"Generalizzazione di",
[Visualizzazione lista prodotti (@uc23)]
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza la lista dei prodotti collocati nei bin"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente richiede la visualizzazione della lista dei prodotti collocati nei bin"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero visualizzare la lista dei prodotti collocati nei bin delle zone dell'ambiente 3D"
)
#printUseCaseInfo(
"Inclusioni",
[Visualizzazione singolo prodotto collocato (@uc23.2.1)]
)
#derivedRequirements("23.2")
===== Visualizzazione singolo prodotto collocato <uc23.2.1>
#printUseCaseInfo(
"Generalizzazione di",
[Visualizzazione singolo prodotto non collocato (@uc23.1.1)]
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha richiesto la visualizzazione della lista dei prodotti collocati nei bin"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza le informazioni relative ad un singolo prodotto, collocato in un bin, presente in lista"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente richiede la visualizzazione della lista dei prodotti collocati nei bin"
)
#printUseCaseInfo(
"Inclusioni",
[Visualizzazione ID zona di appartenenza (@uc23.2.1.1)],
[Visualizzazione ID bin di appartenenza (@uc23.2.1.2)]
)
#derivedRequirements("23.2.1")
====== Visualizzazione ID zona di appartenenza <uc23.2.1.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha richiesto la visualizzazione della lista dei prodotti collocati"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza l'ID della zona di appartenenza del prodotto visualizzato"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente visualizza un elemento della lista dei prodotti collocati"
)
#derivedRequirements("23.2.1.1")
====== Visualizzazione ID bin di appartenenza <uc23.2.1.2>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha richiesto la visualizzazione della lista dei prodotti collocati"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza l'ID del bin dove si trova il prodotto visualizzato"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente visualizza un elemento della lista dei prodotti collocati"
)
#derivedRequirements("23.2.1.2")
=== Ricerca prodotti <uc24>
#figure(
image("./imgs/UC24.svg"),
caption: "Diagramma UC--24"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha richiesto l'importazione dei prodotti",
"Il sistema ha importato correttamente almeno un prodotto"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza i risultati della ricerca filtrati secondo il termine inserito e la modalità scelta"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona la modalità di ricerca tra quelle disponibili",
"L'utente inserisce il termine di ricerca"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero poter ricercare un prodotto per individuarlo velocemente nella lista dei prodotti"
)
#printUseCaseInfo(
"Generalizzazioni",
[Ricerca per ID prodotto (@uc24.1)],
[Ricerca per nome prodotto (@uc24.2)],
[Ricerca per categoria prodotto (@uc24.3)]
)
#derivedRequirements("24")
==== Ricerca per ID prodotto <uc24.1>
#printUseCaseInfo(
"Generalizzazione di",
[Ricerca prodotti (@uc24)]
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza la lista dei prodotti filtrata secondo l'ID del prodotto inserito come termine di ricerca"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce l'ID del prodotto da cercare"
)
#derivedRequirements("24.1")
==== Ricerca per nome prodotto <uc24.2>
#printUseCaseInfo(
"Generalizzazione di",
[Ricerca prodotti (@uc24)]
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza la lista dei prodotti filtrata secondo il nome di prodotto inserito come termine di ricerca"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce il nome del prodotto da cercare"
)
#derivedRequirements("24.2")
==== Ricerca per categoria prodotto <uc24.3>
#printUseCaseInfo(
"Generalizzazione di",
[Ricerca prodotti (@uc24)]
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza la lista dei prodotti filtrata secondo la categoria inserita come termine di ricerca"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente inserisce la categoria di prodotto desiderata"
)
#derivedRequirements("24.3")
=== Spostamento prodotto <uc25>
#figure(
image("./imgs/UC25.svg", width: 120%),
caption: "Diagramma UC--25"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha richiesto l'importazione dei prodotti",
"Il sistema ha importato correttamente almeno un prodotto"
)
#printUseCaseInfo(
"Postcondizioni",
"Il sistema inserisce l'ordine di movimentazione del prodotto verso il bin di destinazione"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente richiede lo spostamento di un prodotto verso un bin di destinazione"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero spostare un prodotto verso un bin di destinazione per poterlo (ri)collocare nell'ambiente 3D"
)
#printUseCaseInfo(
"Generalizzazioni",
[Spostamento prodotto non collocato in un bin (@uc25.1)],
[Spostamento prodotto collocato in un bin (@uc25.2)]
)
#derivedRequirements("25")
==== Spostamento prodotto non collocato in un bin <uc25.1>
#printUseCaseInfo(
"Generalizzazione di",
[Spostamento prodotto (@uc25)]
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il prodotto selezionato non è collocato in un bin",
)
#printUseCaseInfo(
"Inclusioni",
[Invio richiesta di movimentazione (@uc25.3)],
)
#derivedRequirements("25.1")
==== Spostamento prodotto collocato in un bin <uc25.2>
#printUseCaseInfo(
"Generalizzazione di",
[Spostamento prodotto (@uc25)]
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il prodotto selezionato è collocato in un bin",
)
#printUseCaseInfo(
"Estensioni",
[Invio richiesta di movimentazione (@uc25.3)],
[Visualizzazione errore spostamento impossibile (@uc25.2.1)]
)
#derivedRequirements("25.2")
===== Visualizzazione errore spostamento impossibile <uc25.2.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha immesso un ordine di movimentazione per lo spostamento di un prodotto",
"Il bin di destinazione è occupato"
)
#printUseCaseInfo(
"Postcondizioni",
"L'ordine di movimentazione è annullato",
"L'ordine di movimentazione non viene inserito nella cronologia",
"Il prodotto non viene spostato",
"L'utente visualizza un errore relativo all'impossibilità di spostare il prodotto"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente ha richiesto lo spostamento di un prodotto verso un bin già occupato"
)
#derivedRequirements("25.2.1")
==== Invio richiesta di movimentazione <uc25.3>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha richiesto lo spostamento di un prodotto",
"Il bin di destinazione è libero"
)
#printUseCaseInfo(
"Postcondizioni",
"Il sistema inserisce l'ordine di movimentazione del prodotto verso il bin di destinazione"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente seleziona un prodotto",
"L'utente seleziona un bin di destinazione",
"L'utente immette l'odine di movimentazione del prodotto"
)
#printUseCaseInfo(
"Inclusioni",
[Visualizzazione errore spostamento negato (@uc25.3.1)],
[Visualizzazione errore di connessione alla API (@uc25.3.2)],
)
#derivedRequirements("25.3")
===== Visualizzazione errore spostamento negato <uc25.3.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha immesso un ordine di movimentazione per lo spostamento di un prodotto",
"Il sistema ha negato lo spostamento del prodotto"
)
#printUseCaseInfo(
"Postcondizioni",
"L'ordine di movimentazione è annullato",
"L'ordine di movimentazione non viene inserito nella cronologia",
"Il prodotto non viene spostato",
"L'utente visualizza un errore relativo all'impossibilità di spostare il prodotto",
)
#printUseCaseInfo(
"Scenario principale",
"L'utente ha richiesto lo spostamento di un prodotto ma il sistema ha negato la richiesta"
)
#derivedRequirements("25.3.1")
===== Visualizzazione errore di connessione alla API <uc25.3.2>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha immesso un ordine di movimentazione per lo spostamento di un prodotto",
"Il sistema non è connesso alla API"
)
#printUseCaseInfo(
"Postcondizioni",
"L'ordine di movimentazione è annullato",
"L'ordine di movimentazione non viene inserito nella cronologia",
"Il prodotto non viene spostato",
"L'utente visualizza un errore relativo all'impossibilità di connettersi alla API",
)
#printUseCaseInfo(
"Scenario principale",
"L'utente ha richiesto lo spostamento di un prodotto ma la API non ha fornito risposta in tempo utile"
)
#derivedRequirements("25.3.2")
=== Visualizzazione cronologia ordini di movimentazione <uc26>
#figure(
image("./imgs/UC26.svg", width: 115%),
caption: "Diagramma UC--26"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza la cronologia degli ordini di movimentazione immessi"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente richiede la visualizzazione della cronologia degli ordini di movimentazione"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero visualizzare la cronologia degli ordini di movimentazione immessi per poterli monitorare"
)
#printUseCaseInfo(
"Inclusioni",
[Visualizzazione singolo ordine di movimentazione (@uc26.1)]
)
#derivedRequirements("26")
==== Visualizzazione singolo ordine di movimentazione <uc26.1>
#figure(
image("./imgs/UC26.1.svg", width: 80%),
caption: "Diagramma UC--26.1"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha richiesto la visualizzazione della cronologia degli ordini di movimentazione"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza le informazioni relative ad un singolo ordine di movimentazione presente in lista"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente richiede la visualizzazione della cronologia degli ordini di movimentazione"
)
#printUseCaseInfo(
"Inclusioni",
[Visualizzazione ID bin di destinazione (@uc26.1.2)],
[Visualizzazione ID prodotto (@uc26.1.3)],
[Visualizzazione nome prodotto (@uc26.1.4)],
)
#printUseCaseInfo(
"Estensioni",
[Visualizzazione ID bin di partenza (@uc26.1.1)]
)
#derivedRequirements("26.1")
===== Visualizzazione ID bin di partenza <uc26.1.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha richiesto la visualizzazione della cronologia degli ordini di movimentazione",
"L'origine della movimentazione è un bin"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza l'ID del bin di partenza dell'ordine di movimentazione"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente visualizza un ordine di movimentazione presente in lista"
)
#derivedRequirements("26.1.1")
===== Visualizzazione ID bin di destinazione <uc26.1.2>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha richiesto la visualizzazione della cronologia degli ordini di movimentazione"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza l'ID del bin di destinazione dell'ordine di movimentazione"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente visualizza un ordine di movimentazione presente in lista"
)
#derivedRequirements("26.1.2")
===== Visualizzazione ID prodotto <uc26.1.3>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha richiesto la visualizzazione della cronologia degli ordini di movimentazione"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza l'ID del prodotto oggetto dell'ordine di movimentazione"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente visualizza un ordine di movimentazione presente in lista"
)
#derivedRequirements("26.1.3")
===== Visualizzazione nome prodotto <uc26.1.4>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha richiesto la visualizzazione della cronologia degli ordini di movimentazione"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza il nome del prodotto oggetto dell'ordine di movimentazione"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente visualizza un ordine di movimentazione presente in lista"
)
#derivedRequirements("26.1.4")
=== Ispezione ordine di movimentazione <uc27>
#figure(
image("./imgs/UC27.svg"),
caption: "Diagramma UC--27"
)
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"Il sistema è operativo",
"L'utente ha immesso almeno un ordine di movimentazione valido"
)
#printUseCaseInfo(
"Postcondizioni",
"L'utente visualizza i bin coinvolti nell'ordine di movimentazione"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente richiede la visualizzazione dei bin coinvolti nell'ordine di movimentazione"
)
#printUseCaseInfo(
"User story associata",
"Come utente, desidero visualizzare in modo grafico i bin coinvolti nell'ordine di movimentazione"
)
#printUseCaseInfo(
"Inclusioni",
[Evidenziazione bin di destinazione (@uc27.1)]
)
#printUseCaseInfo(
"Estensioni",
[Evidenziazione bin di partenza (@uc27.2)]
)
#derivedRequirements("27")
==== Evidenziazione bin di destinazione <uc27.1>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha richiesto la visualizzazione dei bin coinvolti nell'ordine di movimentazione"
)
#printUseCaseInfo(
"Postcondizioni",
"Il bin di destinazione dell'ordine di movimentazione viene evidenziato graficamente"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente richiede la visualizzazione dei bin coinvolti nell'ordine di movimentazione"
)
#derivedRequirements("27.1")
==== Evidenziazione bin di partenza <uc27.2>
#printUseCaseInfo("Attore principale", "Utente")
#printUseCaseInfo(
"Precondizioni",
"L'utente ha richiesto la visualizzazione dei bin coinvolti nell'ordine di movimentazione",
"L'origine della movimentazione è un bin"
)
#printUseCaseInfo(
"Postcondizioni",
"Il bin di partenza dell'ordine di movimentazione viene evidenziato graficamente"
)
#printUseCaseInfo(
"Scenario principale",
"L'utente richiede la visualizzazione dei bin coinvolti nell'ordine di movimentazione"
)
#derivedRequirements("27.2")
#pagebreak()
#set heading(numbering: "1.1")
// FINE UC
= Requisiti <requisiti>
== Codice identificativo
Ogni requisito è caratterizzato da un codice identificativo definito nel seguente modo:
#align(`[Tipologia][Classificazione]–[Sequenza]`, center)
Dove:
- `Tipologia` può assumere i valori:
- `F`: funzionale;
- `Q`: di qualità;
- `V`: di vincolo.
- `Classificazione` può assumere i valori:
- `M`: mandatory, obbligatorio;
- `D`: desiderabile;
- `O`: opzionale.
- `Sequenza` rappresenta l'identificativo numerico del requisito.
#show figure: set block(breakable: true)
#show ">=": [$>=$]
#show "<=": [$<=$]
== Requisiti funzionali <requisiti-funzionali>
#figure(
table(
columns: (11%, 19%, 50%, 20%),
align: left,
[*Codice*], [*Riferimento*], [*Descrizione*], [*Classificazione*],
..requirements.at("functional").map(item => item.values().slice(0,4).flatten()).flatten()
),
caption: [Requisiti funzionali]
)
#show "#ndp_v": [#ndp_v]
#show "#pdq_v": [#pdq_v]
== Requisiti di qualità <requisiti-qualita>
#figure(
table(
columns: (11%, 19%, 50%, 20%),
align: left,
[*Codice*], [*Riferimento*], [*Descrizione*], [*Classificazione*],
..requirements.at("quality").map(item => item.values().slice(0,4).flatten()).flatten()
),
caption: [Requisiti di qualità]
)
== Requisiti prestazionali <requisiti-prestazioni>
L'analisi dei requisiti condotta da #err418 non ha individuato alcun requisito prestazionale.
== Requisiti di vincolo <requisiti-vincolo><vincoli>
#figure(
table(
columns: (11%, 19%, 50%, 20%),
align: left,
[*Codice*], [*Riferimento*], [*Descrizione*], [*Classificazione*],
..requirements.at("constraints").map(item => item.values().slice(0,4).flatten()).flatten()
),
caption: [Requisiti di vincolo]
)
== Riepilogo requisiti <requisiti-riepilogo>
#let types = ("", "functional", "quality", "constraints", "performance", "security")
#let categories = ("", "Obbligatorio", "Desiderabile", "Opzionale")
#let countRequirements(type, category) = {
if type not in types { panic("Tipologia di requisito errata") }
if category not in categories { panic("Categoria di requisito errata") }
let counter = 0
if (type == "" and category == "") {
for key in requirements.keys() {
counter = counter + requirements.at(key).len()
}
}
else if (type != "" and category == "") {
counter = requirements.at(type).len()
}
else if (type == "" and category != "") {
for key in requirements.keys() {
counter = counter + requirements.at(key).filter(item => item.at("cat") == category).len()
}
}
else if (type != "" and category != "") {
counter = requirements.at(type).filter(item => item.at("cat") == category).len()
}
return counter
}
#figure(
table(
columns: (30%, 16%, 16%, 16%, 12%),
align: left,
[*Tipologia*], [Obbligatori], [Desiderabili], [Opzionali], [*Totale*],
[Requisiti funzionali],
[#countRequirements("functional", "Obbligatorio")],
[#countRequirements("functional", "Desiderabile")],
[#countRequirements("functional", "Opzionale")],
[#countRequirements("functional", "")],
[Requisiti di qualità],
[#countRequirements("quality", "Obbligatorio")],
[#countRequirements("quality", "Desiderabile")],
[#countRequirements("quality", "Opzionale")],
[#countRequirements("quality", "")],
[Requisiti prestazionali],
[#countRequirements("performance", "Obbligatorio")],
[#countRequirements("performance", "Desiderabile")],
[#countRequirements("performance", "Opzionale")],
[#countRequirements("performance", "")],
[Requisiti di vincolo],
[#countRequirements("constraints", "Obbligatorio")],
[#countRequirements("constraints", "Desiderabile")],
[#countRequirements("constraints", "Opzionale")],
[#countRequirements("constraints", "")]
),
caption: [Riepilogo requisiti]
) |
|
https://github.com/typst/packages | https://raw.githubusercontent.com/typst/packages/main/packages/preview/scienceicons/0.0.6/index.typ | typst | Apache License 2.0 | // arxiv
#let arxiv-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M14 9.8l3.5-4.1c.3-.4.4-.6.3-.9-.1-.3-.5-.6-.9-.6-.2 0-.4.1-.6.2L12.2 8 14 9.8zM7.5 20c-.4 0-.8-.3-1-.6-.1-.4 0-.9.3-1.2l3.3-4 .2.2-3.3 4c-.2.2-.3.6-.2.9.1.3.4.4.7.4.2 0 .4-.1.5-.2l6.9-6.4c.3-.3.4-.6.5-1s-.1-.7-.4-1l-.1-.1-8.5-8.1c-.2-.2-.4-.3-.6-.4-.3 0-.6.2-.7.5-.1.2-.1.4.2.8l5 6-.2.2-5-6c-.3-.5-.4-.7-.3-1.1.2-.4.5-.6 1-.6.3.1.6.2.8.5l8.5 8.1.1.1c.3.3.5.8.4 1.2 0 .5-.2.9-.6 1.2l-6.8 6.3c-.1.2-.4.3-.7.3z"/> <path d="M18.9 20.2L12.1 12l-1.8-2.2-1.1 1c-.7.6-.7 1.7 0 2.3l8.7 8.4c.2.2.4.2.6.2.3 0 .6-.2.8-.5 0-.3-.1-.7-.4-1z"/></svg>```.text
#let arxiv-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(arxiv-svg.replace("currentColor", color.to-hex())))
}
// cc-by
#let cc-by-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M12 2.2c2.7 0 5 .9 6.9 2.8 1.9 1.9 2.8 4.2 2.8 6.9s-.9 5-2.8 6.8c-2 1.9-4.3 2.9-7 2.9-2.6 0-4.9-1-6.9-2.9-1.8-1.7-2.8-4-2.8-6.7s1-5 2.9-6.9C7 3.2 9.3 2.2 12 2.2zM12 4c-2.2 0-4.1.8-5.6 2.3C4.8 8 4 9.9 4 12c0 2.2.8 4 2.4 5.6C8 19.2 9.8 20 12 20c2.2 0 4.1-.8 5.7-2.4 1.5-1.5 2.3-3.3 2.3-5.6 0-2.2-.8-4.1-2.3-5.7C16.1 4.8 14.2 4 12 4zm2.6 5.6v4h-1.1v4.7h-3v-4.7H9.4v-4c0-.2.1-.3.2-.4.1-.2.2-.2.4-.2h4c.2 0 .3.1.4.2.2.1.2.2.2.4zm-4-2.5c0-.9.5-1.4 1.4-1.4s1.4.5 1.4 1.4c0 .9-.5 1.4-1.4 1.4s-1.4-.5-1.4-1.4z"/></svg>```.text
#let cc-by-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(cc-by-svg.replace("currentColor", color.to-hex())))
}
// cc-nc
#let cc-nc-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M12 2.2c2.7 0 5 .9 6.9 2.8 1.9 1.9 2.8 4.2 2.8 6.9s-.9 5-2.8 6.8c-2 1.9-4.3 2.9-7 2.9-2.6 0-4.9-1-6.9-2.9-1.9-1.9-2.9-4.2-2.9-6.9s1-5 2.9-6.9c2-1.7 4.3-2.7 7-2.7zM4.4 9.4C4.2 10.2 4 11 4 12c0 2.2.8 4 2.4 5.6C8 19.2 9.8 20 12 20c2.2 0 4.1-.8 5.7-2.4.6-.5 1-1.1 1.3-1.7l-3.7-1.6c-.1.6-.4 1.1-.9 1.5-.5.4-1.1.6-1.8.7V18h-1.1v-1.5c-1.1 0-2.1-.4-3-1.2l1.3-1.4c.6.6 1.4.9 2.2.9.3 0 .6-.1.9-.2.2-.2.4-.4.4-.7 0-.2-.1-.4-.3-.6l-.9-.4-1.1-.6-1.5-.7-5.1-2.2zM12 4c-2.2 0-4.1.8-5.6 2.3-.4.4-.7.9-1.1 1.3L9 9.3c.2-.5.5-.9 1-1.2.5-.3 1-.5 1.6-.5V6.1h1.1v1.5c.9 0 1.7.3 2.4.9l-1.3 1.3c-.5-.4-1.1-.6-1.7-.6-.3 0-.6.1-.8.2-.2.1-.3.3-.3.6 0 .1 0 .2.1.2l1.2.6.9.4 1.6.7 5 2.2c.2-.7.2-1.4.2-2.1 0-2.2-.8-4.1-2.3-5.7C16.1 4.8 14.2 4 12 4z"/></svg>```.text
#let cc-nc-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(cc-nc-svg.replace("currentColor", color.to-hex())))
}
// cc-nd
#let cc-nd-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M12 2.2c2.7 0 5 .9 6.9 2.8 1.9 1.9 2.8 4.2 2.8 6.9s-.9 5-2.8 6.9c-2 1.9-4.3 2.9-7 2.9-2.6 0-4.9-1-6.9-2.9C3.2 17 2.2 14.7 2.2 12s1-5 2.9-6.9C7 3.2 9.3 2.2 12 2.2zM12 4c-2.2 0-4.1.8-5.6 2.4C4.8 8 4 9.9 4 12c0 2.2.8 4 2.4 5.6C8 19.2 9.8 20 12 20c2.2 0 4.1-.8 5.7-2.4 1.5-1.5 2.3-3.3 2.3-5.6 0-2.2-.8-4.1-2.3-5.6C16.1 4.8 14.2 4 12 4zm3.7 5.7v1.7H8.6V9.7h7.1zm0 3.1v1.7H8.6v-1.7h7.1z"/></svg>```.text
#let cc-nd-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(cc-nd-svg.replace("currentColor", color.to-hex())))
}
// cc-sa
#let cc-sa-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M12 2.2c2.7 0 5 .9 6.9 2.8 1.9 1.9 2.8 4.2 2.8 6.9s-.9 5-2.8 6.9c-2 1.9-4.3 2.9-7 2.9-2.6 0-4.9-1-6.9-2.9C3.2 17 2.2 14.7 2.2 12s1-5 2.9-6.9C7 3.2 9.3 2.2 12 2.2zM12 4c-2.2 0-4.1.8-5.6 2.4C4.8 8 4 9.9 4 12c0 2.2.8 4 2.4 5.6C8 19.2 9.8 20 12 20c2.2 0 4.1-.8 5.7-2.4 1.5-1.5 2.3-3.3 2.3-5.6 0-2.2-.8-4.1-2.3-5.6C16.1 4.8 14.2 4 12 4zm-4.3 6.6c.2-1.2.7-2.1 1.4-2.8.8-.7 1.7-1 2.8-1 1.5 0 2.8.5 3.7 1.5.9 1 1.4 2.3 1.4 3.8s-.5 2.7-1.4 3.7c-.9 1-2.2 1.5-3.7 1.5-1.1 0-2.1-.3-2.9-1-.8-.7-1.3-1.6-1.4-2.8h2.5c.1 1.2.8 1.8 2.1 1.8.7 0 1.2-.3 1.7-.9.4-.6.6-1.4.6-2.4s-.2-1.8-.6-2.4c-.4-.5-.9-.8-1.7-.8-1.3 0-2 .6-2.2 1.7h.7l-1.9 1.9-1.9-1.9.8.1z"/></svg>```.text
#let cc-sa-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(cc-sa-svg.replace("currentColor", color.to-hex())))
}
// cc-zero
#let cc-zero-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M12 6.4c-3.2 0-4 3-4 5.6 0 2.6.8 5.6 4 5.6s4-3 4-5.6c0-2.6-.8-5.6-4-5.6zm0 2.1h.4c.2.2.3.5.1.9l-2.1 3.9c-.1-.5-.1-1-.1-1.4 0-1 0-3.4 1.7-3.4zm1.6 1.8c.1.6.1 1.2.1 1.7 0 1.1-.1 3.5-1.7 3.5h-.4-.1-.1c-.4-.2-.6-.4-.3-.9l2.5-4.3z"/> <path d="M12 2.2c-2.7 0-5 .9-6.8 2.8-1 1-1.7 2.1-2.2 3.3-.5 1.2-.8 2.4-.8 3.7 0 1.3.2 2.5.7 3.7.5 1.2 1.2 2.2 2.1 3.2.9.9 2 1.6 3.2 2.1 1.2.5 2.4.7 3.7.7 1.3 0 2.5-.3 3.7-.8 1.2-.5 2.3-1.2 3.2-2.2.9-.9 1.6-1.9 2.1-3.1.5-1.2.7-2.4.7-3.8 0-1.3-.2-2.6-.7-3.7-.3-1-1-2.1-1.9-3-2-1.9-4.3-2.9-7-2.9zM12 4c2.2 0 4.1.8 5.7 2.3.7.8 1.3 1.7 1.7 2.6.4 1 .6 2 .6 3.1 0 2.2-.8 4.1-2.3 5.6-.8.8-1.7 1.4-2.7 1.8-1 .4-2 .6-3 .6-1.1 0-2.1-.2-3-.6-1-.4-1.8-1-2.6-1.7C5.6 16.9 5 16 4.6 15c-.4-1-.6-2-.6-3 0-1.1.2-2.1.6-3 .4-1 1-1.9 1.8-2.6C7.9 4.8 9.8 4 12 4z"/></svg>```.text
#let cc-zero-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(cc-zero-svg.replace("currentColor", color.to-hex())))
}
// cc
#let cc-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M12 2.2c2.7 0 5 1 7 2.9.9.9 1.6 2 2.1 3.1.5 1.2.7 2.4.7 3.8 0 1.3-.2 2.6-.7 3.8-.5 1.2-1.2 2.2-2.1 3.1-1 .9-2 1.7-3.2 2.2-1.2.5-2.5.7-3.7.7s-2.6-.3-3.8-.8c-1.2-.5-2.2-1.2-3.2-2.1s-1.6-2-2.1-3.2-.8-2.4-.8-3.7c0-1.3.2-2.5.7-3.7S4.2 6 5.1 5.1C7 3.2 9.3 2.2 12 2.2zM12 4c-2.2 0-4.1.8-5.6 2.3C5.6 7.1 5 8 4.6 9c-.4 1-.6 2-.6 3s.2 2.1.6 3c.4 1 1 1.8 1.8 2.6S8 19 9 19.4c1 .4 2 .6 3 .6s2.1-.2 3-.6c1-.4 1.9-1 2.7-1.8 1.5-1.5 2.3-3.3 2.3-5.6 0-1.1-.2-2.1-.6-3.1-.4-1-1-1.8-1.7-2.6C16.1 4.8 14.2 4 12 4zm-.1 6.4l-1.3.7c-.1-.3-.3-.5-.5-.6-.2-.1-.4-.2-.6-.2-.9 0-1.3.6-1.3 1.7 0 .5.1.9.3 1.3.2.3.5.5 1 .5.6 0 1-.3 1.2-.8l1.2.6c-.3.5-.6.9-1.1 1.1-.5.3-1 .4-1.5.4-.9 0-1.6-.3-2.1-.8-.5-.6-.8-1.3-.8-2.3 0-.9.3-1.7.8-2.2.6-.6 1.3-.8 2.1-.8 1.2 0 2.1.4 2.6 1.4zm5.6 0l-1.3.7c-.1-.3-.3-.5-.5-.6-.2-.1-.4-.2-.6-.2-.9 0-1.3.6-1.3 1.7 0 .5.1.9.3 1.3.2.3.5.5 1 .5.6 0 1-.3 1.2-.8l1.2.6c-.3.5-.6.9-1.1 1.1-.4.2-.9.3-1.4.3-.9 0-1.6-.3-2.1-.8s-.8-1.3-.8-2.2c0-.9.3-1.7.8-2.2.5-.5 1.2-.8 2-.8 1.2 0 2.1.4 2.6 1.4z"/></svg>```.text
#let cc-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(cc-svg.replace("currentColor", color.to-hex())))
}
// curvenote
#let curvenote-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M21.8 17.3c0 2.5-1.9 4.4-4.4 4.4-2.4 0-4.4-1.9-4.4-4.4s1.9-4.4 4.4-4.4c2.3 0 4.4 2.1 4.4 4.4zM2.2 12.9H11v8.8c-4.8 0-8.8-3.9-8.8-8.8zm2.7-8.1C6.5 3.2 8.8 2.2 11 2.2V11H2.2c0-2.3 1-4.5 2.7-6.2zm14.2 3.6C17.5 10 15.2 11 13 11V2.2h8.8c0 2.3-1 4.6-2.7 6.2z"/></svg>```.text
#let curvenote-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(curvenote-svg.replace("currentColor", color.to-hex())))
}
// discord
#let discord-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M19.7 4.9c-1.5-.7-3-1.1-4.6-1.4-.2.3-.5.8-.6 1.1-1.7-.2-3.4-.2-5.1 0-.2-.3-.3-.7-.5-1-1.6.2-3.1.8-4.6 1.3C1.4 9.2.6 13.4 1 17.6c1.7 1.3 3.6 2.2 5.6 2.9.5-.6.8-1.3 1.3-2-.7-.2-1.3-.6-2-.9.1-.1.3-.2.5-.3 3.6 1.7 7.7 1.7 11.3 0 .1.1.3.2.5.3-.6.3-1.3.7-2 .9.3.7.8 1.4 1.3 2 2.1-.6 3.9-1.6 5.6-2.9.4-4.8-.9-9-3.4-12.7zM8.3 15c-1.1 0-2-1-2-2.2s.9-2.2 2-2.2 2.1 1 2 2.2-.8 2.2-2 2.2zm7.4 0c-1.1 0-2-1-2-2.2s.9-2.2 2-2.2 2.1 1 2 2.2-.9 2.2-2 2.2z"/></svg>```.text
#let discord-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(discord-svg.replace("currentColor", color.to-hex())))
}
// email
#let email-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M21.8 18c0 1.1-.9 2-1.9 2H4.2c-1.1 0-1.9-.9-1.9-2V9.9c0-.5.3-.7.8-.4l7.8 4.7c.7.4 1.7.4 2.4 0L21 9.5c.4-.2.8-.1.8.4V18z"/> <path d="M21.8 6c0-1.1-.9-2-1.9-2H4.2c-1.1 0-2 .9-2 2v.4c0 .5.3 1.1.8 1.3l8.5 5.1c.2.1.7.1.9 0l8.6-5c.4-.3.8-.9.8-1.3-.1-.1-.1-.5 0-.5z"/></svg>```.text
#let email-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(email-svg.replace("currentColor", color.to-hex())))
}
// github
#let github-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M12 2.5c-5.4 0-9.8 4.4-9.8 9.7 0 4.3 2.8 8 6.7 9.2.5.1.7-.2.7-.5v-1.8c-2.4.5-3.1-.6-3.3-1.1-.1-.3-.6-1.1-1-1.4-.3-.2-.8-.6 0-.6s1.3.7 1.5 1c.9 1.5 2.3 1.1 2.8.8.1-.6.3-1.1.6-1.3-2.2-.2-4.4-1.1-4.4-4.8 0-1.1.4-1.9 1-2.6-.1-.2-.4-1.2.1-2.6 0 0 .8-.3 2.7 1 .8-.2 1.6-.3 2.4-.3.8 0 1.7.1 2.4.3 1.9-1.3 2.7-1 2.7-1 .5 1.3.2 2.3.1 2.6.6.7 1 1.5 1 2.6 0 3.7-2.3 4.6-4.4 4.8.4.3.7.9.7 1.8V21c0 .3.2.6.7.5 3.9-1.3 6.6-4.9 6.6-9.2 0-5.4-4.4-9.8-9.8-9.8z"/></svg>```.text
#let github-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(github-svg.replace("currentColor", color.to-hex())))
}
// jupyter-book
#let jupyter-book-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M11.3 20.5c0-1.4-.8-2.1-2.4-2.1h-2c-1.2 0-2.2-.3-3-.9-.7-.6-1.3-1.5-1.6-2.6l1.1-.4c.4 1.3 1.5 2.1 3.3 2.1h2.2c1.5 0 2.6.6 3.1 1.8.5-1.2 1.6-1.8 3.1-1.8h2c1.9 0 3-.7 3.5-2.1l1.1.4c-.3 1.2-.9 2.1-1.6 2.6-.7.6-1.7.9-3 .9H15c-1.6 0-2.4.7-2.4 2.1M7.1 13.4c-.5 0-1-.1-1.5-.3-.4-.2-.8-.6-1.1-1-.3-.5-.4-1.1-.4-1.6h1.3c0 .7.2 1.1.4 1.4.3.3.8.5 1.2.5.3 0 .6-.1.9-.2.2-.2.4-.4.5-.7.1-.3.2-.6.2-1v-6l-1.2-.1v-.9h3.7v.8l-1.1.2v5.9c0 .5-.1 1-.3 1.5-.2.4-.6.8-1 1-.5.4-1 .5-1.6.5zm5-.2v-.8l1.1-.2V4.5l-1.1-.2v-.8h4.2c1 0 1.8.2 2.4.7.6.4.9 1.1.9 2 0 .4-.1.8-.4 1.2-.3.3-.7.6-1.1.8.4.1.7.2 1 .5.3.2.5.5.7.9.2.3.2.7.2 1.1 0 .9-.3 1.6-.9 2s-1.4.7-2.4.7l-4.6-.2zm2.4-1h2.2c.5 0 1-.1 1.4-.4.3-.3.5-.8.5-1.3 0-.3-.1-.7-.2-1-.1-.3-.3-.5-.6-.6-.3-.2-.6-.2-1-.2h-2.4l.1 3.5zm0-4.6h2.1c.4 0 .8-.1 1.1-.4.3-.3.5-.7.4-1.1 0-.4-.2-.9-.5-1.2-.4-.3-.9-.4-1.4-.4h-1.8l.1 3.1z"/></svg>```.text
#let jupyter-book-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(jupyter-book-svg.replace("currentColor", color.to-hex())))
}
// jupyter-text
#let jupyter-text-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M2.9 12.5c0 .7-.1 1-.2 1.1-.2.1-.4.2-.6.2l.1.4c.3 0 .7-.1.9-.3.3-.3.4-.8.4-1.2V10h-.6v2.5zM7 12.2v.8h-.4v-.5c-.2.4-.6.6-1 .6-.5 0-1.1-.3-1.1-1.3V10H5v1.7c0 .6.2 1 .7 1 .4 0 .8-.3.8-.8V10H7v2.2zM8.1 11v-1h.5v.5c.2-.4.6-.6 1.1-.6.7 0 1.3.6 1.3 1.5 0 1.1-.7 1.6-1.4 1.6-.4 0-.7-.2-.9-.5v1.7h-.6V11zm.5.8v.2c0 .2.4.6.8.6.6 0 .9-.5.9-1.2 0-.6-.3-1.1-.9-1.1-.5 0-.8.4-.8.9v.6zM11.9 10l.7 1.8.2.6.2-.6.6-1.8h.6l-.8 2.2c-.4 1-.7 1.6-1 1.9-.2.2-.4.3-.7.4l-.1-.5c.2-.1.3-.1.5-.3s.4-.4.5-.6v-.2L11.3 10h.6zM15.7 9.1v.9h.8v.4h-.8V12c0 .4.1.6.4.6h.3v.4c-.2.1-.3.1-.5.1s-.5-.1-.6-.2c-.2-.2-.2-.5-.2-.8v-1.7h-.5V10h.5v-.7l.6-.2zM17.5 11.6c0 .5.4 1 .9 1h.2c.3 0 .6 0 .8-.2l.1.4c-.3.1-.7.2-1 .2-.8.1-1.4-.5-1.5-1.3v-.2c0-.9.5-1.6 1.4-1.6 1 0 1.2.9 1.2 1.4v.3h-2.1zm1.6-.4c.1-.4-.2-.8-.7-.9h-.1c-.5 0-.8.4-.8.9h1.6zM20.4 10.9V10h.5v.6c.1-.4.4-.6.8-.7h.2v.5h-.2c-.4 0-.7.3-.7.7V13h-.5l-.1-2.1zM20.2 1.7c0 .8-.5 1.4-1.3 1.5-.8 0-1.4-.5-1.5-1.3 0-.8.5-1.4 1.3-1.5.8-.1 1.5.5 1.5 1.3zM12 17.9c-3.7 0-7-1.3-8.7-3.3 1.8 4.8 7.1 7.3 11.9 5.5 2.5-.9 4.5-2.9 5.5-5.5-1.7 2-4.9 3.3-8.7 3.3zM12 5.1c3.7 0 7 1.3 8.7 3.3-1.8-4.8-7.1-7.3-11.9-5.5-2.5.9-4.5 2.9-5.5 5.5 1.7-2 5-3.3 8.7-3.3zM6.9 21.8c.1 1-.7 1.8-1.7 1.9S3.4 23 3.3 22c0-1 .7-1.8 1.7-1.9 1-.1 1.8.7 1.9 1.7zM3.7 4.6c-.6 0-1-.4-1-1s.4-1 1-1 1 .4 1 1c0 .5-.4 1-1 1z"/></svg>```.text
#let jupyter-text-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(jupyter-text-svg.replace("currentColor", color.to-hex())))
}
// jupyter
#let jupyter-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M20.2 1.7c0 .8-.5 1.4-1.3 1.5-.8 0-1.4-.5-1.5-1.3 0-.8.5-1.4 1.3-1.5.8-.1 1.5.5 1.5 1.3zM12 17.9c-3.7 0-7-1.3-8.7-3.3 1.8 4.8 7.1 7.3 11.9 5.5 2.5-.9 4.5-2.9 5.5-5.5-1.7 2-4.9 3.3-8.7 3.3zM12 5.1c3.7 0 7 1.3 8.7 3.3-1.8-4.8-7.1-7.3-11.9-5.5-2.5.9-4.5 2.9-5.5 5.5 1.7-2 5-3.3 8.7-3.3zM6.9 21.8c.1 1-.7 1.8-1.7 1.9-1 .1-1.8-.7-1.9-1.7 0-1 .7-1.8 1.7-1.9 1-.1 1.8.7 1.9 1.7zM3.7 4.6c-.6 0-1-.4-1-1s.4-1 1-1 1 .4 1 1c0 .5-.4 1-1 1z"/></svg>```.text
#let jupyter-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(jupyter-svg.replace("currentColor", color.to-hex())))
}
// linkedin
#let linkedin-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M6.8 8.5H2.9c-.2 0-.3.2-.3.3v12.6c0 .2.2.3.3.3h3.9c.2 0 .3-.2.3-.3V8.8c0-.2-.1-.3-.3-.3zm-2-6.3c-1.4 0-2.6 1.2-2.6 2.6s1.2 2.6 2.6 2.6 2.6-1.2 2.6-2.6-1.2-2.6-2.6-2.6zm11.9 6c-1.6 0-2.7.7-3.4 1.4v-.8c0-.2-.2-.3-.3-.3H9.2c-.2 0-.3.2-.3.3v12.6c0 .2.2.3.3.3h3.9c.2 0 .3-.2.3-.3v-6.3c0-2.1.6-2.9 2-2.9 1.6 0 1.7 1.3 1.7 3v6.1c0 .2.2.3.3.3h3.9c.2 0 .3-.2.3-.3v-6.9c.1-3.1-.5-6.2-4.9-6.2z"/></svg>```.text
#let linkedin-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(linkedin-svg.replace("currentColor", color.to-hex())))
}
// mastodon
#let mastodon-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M21.1 8.7c0-4.2-2.8-5.5-2.8-5.5-1.4-.6-3.8-.9-6.3-.9s-4.9.3-6.3.9c0 0-2.8 1.2-2.8 5.5v3.4c.1 4.1.8 8.2 4.6 9.2 1.8.5 3.3.6 4.5.5 2.2-.1 3.5-.8 3.5-.8l-.1-1.6s-1.6.5-3.4.4c-1.8-.1-3.6-.2-3.9-2.3v-.6s1.7.4 3.9.5c1.3.1 2.6-.1 3.9-.2 2.4-.3 4.6-1.8 4.8-3.2.4-2.2.4-5.3.4-5.3zm-3.3 5.4h-2v-5c0-1-.4-1.6-1.3-1.6-1 0-1.5.6-1.5 1.9v2.7h-2V9.4c0-1.2-.5-1.9-1.5-1.9-.9 0-1.3.5-1.3 1.6v5h-2V9c0-1 .3-1.9.8-2.5.6-.6 1.3-.9 2.2-.9 1 0 1.8.4 2.3 1.2l.5.8.5-.8c.5-.8 1.3-1.2 2.4-1.2.9 0 1.6.3 2.2.9.5.6.8 1.4.8 2.5v5.1z"/></svg>```.text
#let mastodon-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(mastodon-svg.replace("currentColor", color.to-hex())))
}
// myst
#let myst-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M5.7 13.4v-.9l1.1-.2V4.5l-1.1-.1v-.9h2.9l3.2 7.6L15 3.5h3v.9l-1.1.2v7.8l1.1.2v.9h-3.6v-.9l1.2-.2v-7l-3.2 7.7h-.9L8.1 5.3v7l1.2.2v.9H5.7zm5.6 7.1c0-1.4-.8-2.1-2.4-2.1h-2c-1.2 0-2.2-.3-3-.9-.7-.6-1.3-1.5-1.6-2.6l1.1-.4c.4 1.3 1.5 2.1 3.3 2.1h2.2c1.5 0 2.6.6 3.1 1.8.5-1.2 1.6-1.8 3.1-1.8h2c1.9 0 3-.7 3.5-2.1l1.1.4c-.3 1.2-.9 2.1-1.6 2.6-.7.6-1.7.9-3 .9H15c-1.6 0-2.4.7-2.4 2.1"/></svg>```.text
#let myst-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(myst-svg.replace("currentColor", color.to-hex())))
}
// open-access
#let open-access-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M17.1 12.6h-2V7.5c0-1.7-1.4-3.1-3-3.1-.8 0-1.6.3-2.2.9-.6.5-.9 1.3-.9 2.2v.7H7v-.7c0-1.4.5-2.7 1.5-3.7s2.2-1.5 3.6-1.5 2.6.5 3.6 1.5 1.5 2.3 1.5 3.7v5.1z"/> <path d="M12 21.8c-.8 0-1.6-.2-2.3-.5-.7-.3-1.4-.8-1.9-1.3-.6-.6-1-1.2-1.3-2-.3-.8-.5-1.6-.5-2.4s.2-1.6.5-2.4c.3-.7.7-1.4 1.3-2s1.2-1 1.9-1.3c.7-.3 1.5-.5 2.3-.5.8 0 1.6.2 2.3.5.7.3 1.4.8 1.9 1.3.6.6 1 1.2 1.3 2 .3.8.5 1.6.5 2.4s-.2 1.6-.5 2.4c-.3.7-.7 1.4-1.3 2-.6.6-1.2 1-1.9 1.3-.7.3-1.5.5-2.3.5zm0-10.3c-2.2 0-4 1.8-4 4.1s1.8 4.1 4 4.1 4-1.8 4-4.1-1.8-4.1-4-4.1z"/> <circle cx="12" cy="15.6" r="1.7"/></svg>```.text
#let open-access-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(open-access-svg.replace("currentColor", color.to-hex())))
}
// orcid
#let orcid-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M21.8 12c0 5.4-4.4 9.8-9.8 9.8S2.2 17.4 2.2 12 6.6 2.2 12 2.2s9.8 4.4 9.8 9.8zM8.2 5.8c-.4 0-.8.3-.8.8s.3.8.8.8.8-.4.8-.8-.3-.8-.8-.8zm2.3 9.6h1.2v-6h1.8c2.3 0 3.3 1.4 3.3 3s-1.5 3-3.3 3h-3v1.1H9V8.3H7.7v8.2h5.9c3.3 0 4.5-2.2 4.5-4.1s-1.2-4.1-4.3-4.1h-3.2l-.1 7.1z"/></svg>```.text
#let orcid-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(orcid-svg.replace("currentColor", color.to-hex())))
}
// osi
#let osi-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M13.2 15.6c1.4-.5 2.1-1.6 2.1-3.3S13.8 8.9 12 8.9c-1.9 0-3.3 1.6-3.3 3.3 0 1.8.8 3 2.2 3.4l-2.3 5.9c-3.1-.8-6.3-4.6-6.3-9.3 0-5.5 4.3-10 9.7-10s9.8 4.5 9.8 10c0 4.7-3.1 8.5-6.3 9.3l-2.3-5.9z"/></svg>```.text
#let osi-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(osi-svg.replace("currentColor", color.to-hex())))
}
// ror
#let ror-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M10 4.2L8.3 6.8 6.6 4.2H10zM17.1 4.2l-1.7 2.6-1.7-2.6h3.4zM6.6 19.8l1.7-2.6 1.7 2.6H6.6zM13.7 19.8l1.7-2.6 1.7 2.6h-3.4zM20.8 12.5c.6-.1 1.1-.4 1.4-.8.3-.4.5-.9.5-1.5 0-.5-.1-.9-.3-1.2-.2-.3-.4-.6-.7-.8-.3-.2-.6-.3-1-.4-.4-.1-.8-.1-1.2-.1h-3.3v2.6c0-.1-.1-.2-.1-.2-.2-.6-.6-1-1-1.4-.4-.4-.9-.7-1.5-.9-.6-.2-1.2-.3-1.9-.3s-1.3.1-1.9.3c-.5.1-1 .4-1.4.8-.3.4-.6.8-.9 1.3 0-.3-.1-.6-.2-.9-.2-.4-.4-.6-.7-.8-.3-.2-.6-.3-1-.4s-.8-.2-1.3-.2H1v8.5h1.9v-3.4h.9l1.8 3.4h2.3l-2.2-3.6c.6-.1 1.1-.4 1.4-.8v-.1.2c0 .7.1 1.3.3 1.8.2.6.6 1 1 1.4.4.4.9.7 1.5.9.6.2 1.2.3 1.9.3s1.3-.1 1.9-.3c.6-.2 1.1-.5 1.5-.9.4-.4.7-.9 1-1.4 0-.1.1-.2.1-.2V16H18v-3.4h.9l1.8 3.4H23l-2.2-3.5zM5.4 10.7c-.1.2-.2.3-.3.3-.2.1-.3.1-.5.1H2.9V9.2h1.7c.2 0 .3.1.5.1.1.1.3.2.3.3.1.1.1.3.1.5.1.3 0 .5-.1.6zm8.8 2.3c-.1.3-.3.6-.5.9-.2.2-.5.4-.8.6-.3.1-.7.2-1.1.2-.4 0-.8-.1-1.1-.2-.3-.1-.6-.3-.8-.6-.2-.2-.4-.5-.5-.9-.1-.3-.2-.7-.2-1.1 0-.4.1-.8.2-1.1s.3-.6.5-.9c.2-.2.5-.4.8-.6.3-.1.7-.2 1.1-.2.4 0 .8.1 1.1.2.3.1.6.3.8.6.2.2.4.5.5.9.1.3.2.7.2 1.1 0 .4 0 .7-.2 1.1zm6.4-2.3c-.1.1-.2.2-.4.3-.2.1-.3.1-.5.1H18V9.2h1.7c.2 0 .3.1.5.1.1.1.3.2.3.3.1.1.1.3.1.5.1.3.1.5 0 .6z"/></svg>```.text
#let ror-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(ror-svg.replace("currentColor", color.to-hex())))
}
// slack
#let slack-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M6.3 14.6c0 1.1-.9 2-2 2s-2-.9-2-2 .9-2 2-2h2v2zm1.1 0c0-1.1.9-2 2-2s2 .9 2 2v5.1c0 1.1-.9 2-2 2s-2-.9-2-2v-5.1zm2-8.3c-1.1 0-2-.9-2-2s.9-2 2-2 2 .9 2 2v2h-2zm0 1.1c1.1 0 2 .9 2 2s-.9 2-2 2H4.3c-1.1 0-2-.9-2-2s.9-2 2-2h5.1zm8.3 2c0-1.1.9-2 2-2s2 .9 2 2-.9 2-2 2h-2v-2zm-1.1 0c0 1.1-.9 2-2 2s-2-.9-2-2V4.3c0-1.1.9-2 2-2s2 .9 2 2v5.1zm-2 8.3c1.1 0 2 .9 2 2s-.9 2-2 2-2-.9-2-2v-2h2zm0-1.1c-1.1 0-2-.9-2-2s.9-2 2-2h5.1c1.1 0 2 .9 2 2s-.9 2-2 2h-5.1z"/></svg>```.text
#let slack-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(slack-svg.replace("currentColor", color.to-hex())))
}
// twitter
#let twitter-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M22.7 5.4c-.8.3-1.7.6-2.5.7.9-.5 1.6-1.4 1.9-2.4-.9.5-1.8.9-2.8 1.1-1.7-1.8-4.4-1.9-6.2-.2-1.1 1.1-1.6 2.7-1.3 4.2-3.5-.3-6.8-1.9-9-4.7-.4.7-.6 1.5-.6 2.2 0 1.5.7 2.8 1.9 3.6-.7 0-1.4-.2-2-.5v.1c0 2.1 1.5 3.9 3.5 4.3-.6.2-1.3.2-2 .1.6 1.8 2.2 3 4.1 3-1.6 1.2-3.5 1.9-5.4 1.9-.3 0-.7 0-1-.1 2 1.3 4.3 2 6.7 2 8.1 0 12.5-6.7 12.5-12.5v-.6c.8-.6 1.6-1.3 2.2-2.2"/></svg>```.text
#let twitter-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(twitter-svg.replace("currentColor", color.to-hex())))
}
// website
#let website-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M11.9 21.6c-5.3 0-9.7-4.3-9.7-9.7 0-5.3 4.3-9.7 9.7-9.7h.1c2.6 0 5 1 6.8 2.8 1.8 1.8 2.8 4.2 2.8 6.8 0 2.6-1 5-2.8 6.9-1.8 1.9-4.2 2.9-6.9 2.9.1 0 .1 0 0 0zm0-18.2c-4.7 0-8.5 3.9-8.4 8.5 0 4.7 3.8 8.4 8.5 8.4 2.3 0 4.4-.9 6-2.5 1.6-1.6 2.5-3.7 2.5-6s-.9-4.4-2.5-6c-1.6-1.5-3.8-2.4-6.1-2.4zM11 21.2c-.5-.4-1-.9-1.4-1.4-.8-1-1.5-2.1-2-3.2-.8.3-1.7.8-2.4 1.3l-.5-.7c.8-.6 1.7-1.1 2.6-1.4-.4-1.1-.6-2.2-.6-3.4H2.9v-.8h3.8v-.5c.1-1.1.3-2.1.6-3-.9-.4-1.8-.9-2.6-1.5l.5-.6c.8.6 1.6 1 2.5 1.3C8.3 5.6 9.5 4 11 2.7l.5.6C10.1 4.5 9.1 6 8.4 7.6c1 .3 2.1.5 3.1.5V2.8h.8v5.3c1.1 0 2.1-.2 3.1-.5-.4-1-1-2-1.8-2.9-.4-.5-.9-.9-1.3-1.3l.5-.6c.5.4 1 .9 1.4 1.4.8 1 1.5 2 1.9 3.2 1-.4 1.9-.9 2.6-1.4l.5.7c-.8.6-1.7 1.1-2.7 1.4.4 1.1.6 2.2.6 3.4H21v.8h-3.8v.6c-.1.9-.3 1.9-.6 2.8.9.4 1.8.8 2.6 1.4l-.5.7c-.8-.5-1.6-1-2.4-1.3-.7 1.8-1.9 3.4-3.4 4.7l-.5-.6c1.4-1.2 2.5-2.7 3.1-4.3-1-.3-2.1-.5-3.2-.6V21h-.8v-5.3c-1.1 0-2.1.2-3.2.6.4 1.1 1 2.1 1.8 3 .4.5.9.9 1.3 1.3l-.4.6zm-3.5-8.9c0 1.1.2 2.1.5 3.1 1.1-.4 2.3-.6 3.4-.6v-2.5H7.5zm4.9 2.5c1.2 0 2.3.2 3.4.6.3-.8.4-1.7.5-2.5v-.6h-4v2.5zm0-3.3h4c0-1.1-.2-2.1-.6-3.1-1.1.4-2.3.6-3.4.6v2.5zm-4.9 0h4V9c-1.2 0-2.3-.2-3.4-.6-.3.8-.5 1.7-.5 2.6 0 .2 0 .3-.1.5z"/></svg>```.text
#let website-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(website-svg.replace("currentColor", color.to-hex())))
}
// youtube
#let youtube-svg = ```<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="currentColor" aria-hidden="true"> <path d="M21.3 7.2c-.2-.8-.9-1.5-1.7-1.7-1.5-.4-7.6-.4-7.6-.4s-6.1 0-7.6.4c-.9.2-1.6.9-1.8 1.7-.4 1.5-.4 4.7-.4 4.7s0 3.2.4 4.7c.2.8.9 1.5 1.7 1.7 1.5.4 7.6.4 7.6.4s6.1 0 7.6-.4c.8-.2 1.5-.9 1.7-1.7.4-1.5.4-4.7.4-4.7s.1-3.2-.3-4.7zm-6.2 4.7L10 14.8V9l5.1 2.9z"/></svg>```.text
#let youtube-icon(color: black, height: 1.1em, baseline: 13.5%) = {
box(height: height, baseline: baseline, image.decode(youtube-svg.replace("currentColor", color.to-hex())))
} |
https://github.com/jgm/typst-hs | https://raw.githubusercontent.com/jgm/typst-hs/main/test/typ/compiler/closure-20.typ | typst | Other | // Error: 11 expected comma
#let foo(_: 3) = none
|
https://github.com/typst/packages | https://raw.githubusercontent.com/typst/packages/main/packages/preview/genealotree/0.1.0/README.md | markdown | Apache License 2.0 | # Presentation
Genealotree is a typst package to draw genealogical trees.
It is developped at https://codeberg.org/drloiseau/genealogy. This is the place you can get the developpement version and send issues and pull requests.
This package is based on [CeTZ]("https://typst.app/universe/package/cetz/") and it provides functions to draw genealogical trees. It is oriented towards medical genealogy to study genetic disorders inheritance, but you might be able to use it to draw your family tree.
**Features :**
- Draw an unlimited number of independant genealogical trees
- Supports consanguinity and unions between different trees (see limitations)
- Auto adjusts position of children to optimize spacing
- Customize all lengths
- Draw as much phenotypes as needed by coloring individuals
- Print genotype and/or phenotype labels under individuals
**Limitations :**
- Must manually adjust individual position in the tree when drawing consanguinity and unions between trees to prevent overlapping of individuals.
- No remarriages (might be added in a future version)
- No union between individuals at different generations (might be added in a future version)
**To be implemented :**
- Allow to pass CeTZ arguments to every elements to cutomize their appearance
- Draw optional legends for tree symbols and for phenotypes
# Usage
See example.typ for a simple usage example, and the manual for precise references at [manual.pdf](https://codeberg.org/attachments/cfdad2b7-52ae-4e18-8d7b-453fadc45532)
The steps to produce a tree are :
- Import the package and CeTZ
```typ
#import "@preview/genealotree:0.1.0": *
#import "@preview/cetz:0.2.2": canvas
```
- Create a genealogy object
```typ
let my-geneal = genealogy-init()
```
- Add persons to the object : pass a dictionary mapping a persons name with a dictionary describing its characteristics. See the manual for a full reference.
```typ
let my-geneal = add-persons(
my-geneal,
(
"I1": (sex: "m"),
"I2": (sex: "f"),
"II1": (sex: "f"),
)
)
```
- Set unions between persons : give the parents names as an array of 2 strings, and the children names as an array of strings.
```typ
let my-geneal = add-unions(
my-geneal,
(("I1", "I2"), ("II1",))
)
```
- Open up a CeTZ canva and draw the tree
```typ
#canvas(length: 0.4cm, {
draw-tree(my-geneal)
})
```
|
https://github.com/dismint/docmint | https://raw.githubusercontent.com/dismint/docmint/main/random/rust.typ | typst | #import "template.typ": *
#show: template.with(
title: "Rust Guide",
subtitle: "<NAME>"
)
= Introduction
== A basic Rust program
```rust
fn main() {
println!("Hello, world!");
}
```
- Rust uses 4 spaces as their indentation convention.
== Cargo
Cargo is a useful tool for Rust that manages packages as well as makes compilation and running of Rust smoother. `cargo run` can be used to `cargo build` the `src` directory, then run the built binary. You can also run `cargo check` to see if the program will compile, which has the benefit of running extremely quickly.
The `Cargo.lock` file freezes the package versions specified in `Cargo.toml`, meaning that the setup remains reproducible, even as packages update and get newer versions.
== Basic Facts
- Variable in Rust declared with `let` are *immutable* by default. You need to specify mutability with the `mut` keyword.
- Matching is an important construct in Rust.
- The `Result` data type can either take on the `Ok` or `Err` values. We can match the result, or we can also call `.expect()` to throw an error if the value is `Err`, otherwise returning the `Ok` data.
= Common Programming Concepts
== Variables and Mutability
Variables declared with `let` are *immutable* by default, and need to be prefixed with `mut` in order to obtain mutability.
```rust
let x = 5;
let mut x = 5;
```
Variables can also be declared with `const`. Constant variables can be put in the global scope, but are always immutable and cannot take on values that are only able to be computed at runtime.
By shadowing variables, we can have some interesting interactions in Rust.
```rust
fn main() {
let x = 5;
// x= 5
let x = x + 1;
// x = 6
{
let x = x * 2;
// x = 12
}
// x = 6
}
```
This is also an effective way to chance the type of a variable, by redeclaring and shadowing the old variable.
== Data Types
We annotate types with a colon after the name.
```rust
let x: u64;
```
Interestingly, Rust in debug mode reports overflows as an error, but does not do so in release mode, and instead uses complement wrapping.
=== Scalar Types
- `int` types `i32, u8`
- `float` types `f32, f64`
- `bool` can be `true, false`
- `char` can be `'<char>'`
Dividing two integers, results in another integer.
=== Compound Types
Tuples are very similar to Python.
```rust
fn main() {
let tup = (500, 6.4, 1);
let (x, y, z) = tup;
let x = tup.0;
println!("The value of y is: {y}");
}
```
Tuples can be indexed using a dot `(.)`, with the index of the desired value. We can also see above a basic example of *destructuring*.
#define(
title: "Unit"
)[
A tuple without any elements is called a *unit*, which is the default return type for a function.
]
Arrays in Rust must be a *fixed* length.
```rust
fn main() {
let a = [1, 2, 3, 4, 5];
let a: [i32; 5] = [1, 2, 3, 4, 5];
// fills length 5 array with 3's
let a = [3; 5];
}
```
== Functions
Rust doesn't care about where you define your functions, as long as they are visible in the scope of their caller.
```rust
fn test(x: i32, y: char) {}
```
There is an important distinction between an `expression` and a `statement` in Rust. We can't use the value of a statement like we can in some languages. However, we can do something interesting in rust with brackets `{}`. Since brackets constitute an expression, we can have it evaluate to a specific value by making the last line an expression without the semicolon.
```rust
// this block of code as an expression evaluates to 4
{
let x = 3;
x + 1
}
```
You can specify the return type of a function, and Rust will automatically return the last line as long as it is an expression.
```rust
fn five() -> i32 {
5
}
```
== Control Flow
In Rust, similarly to Python, parenthesis on control keywords are generally not needed. Rust will not implicitly convert one type to another, for example an integer to a boolean, so all checks must be made with this in mind.
== If
```rust
fn main() {
let number = 6;
if number % 4 == 0 {
println!("number is divisible by 4");
} else if number % 3 == 0 {
println!("number is divisible by 3");
} else if number % 2 == 0 {
println!("number is divisible by 2");
} else {
println!("number is not divisible by 4, 3, or 2");
}
}
```
We can also use `if` in a Python-like way:
```rust
fn main() {
let condition = true;
let number = if condition { 5 } else { 6 };
println!("The value of number is: {number}");
}
```
== Looping
You can loop infinitely with `loop`. One cool feature of Rust is that the `break` keyword can be used as a pseudo `return`, and the entire loop can be used as an expression. In addition, you can also labels loops to break out multiple layers, or otherwise control the flow of the program.
```rust
fn main() {
let val = 'outer: loop {
loop {
break 'outer 10;
}
};
println!("{val}");
}
```
Other types of loop include the traditional `while` and `for` loops.
```rust
for i in 0..10 {
println!("{i}");
}
```
= Ownership
s
|
|
https://github.com/Ttajika/typst_slide | https://raw.githubusercontent.com/Ttajika/typst_slide/main/library/theme.typ | typst | #import "@preview/cetz:0.2.2"
#import "functions.typ":*
//--------BlackBoardのテーマ
//Headerスライドのデザイン
#let BB-header_slide(title,now:0, end:0,color:"", tcolor:"", current-headings: "", outline: false) = {
set text(size: 23pt, weight:700)
let a = {if outline == true{1} else {0}}
if outline == true {pad(top:30pt,bottom:-30pt)[
#heading-outline(color:color, current-headings: current-headings)]
v(-13pt)
}
pad(left: -20pt, top:30pt)[
#if title == [] { v(20pt) }else { h(20pt);text(size:1.2em)[#title]; h(1fr); text(size:0.7em)[#now/#end]; v(-15pt) }
#line(
length: 30cm,
stroke: 4pt + tcolor.lighten(80%),
) #v(a*2.5em)
]
}
//タイトルスライドのデザイン
#let BB-title_slide(now:0,end:0, color:"",tcolor:"", outline:"", title:"", title_notes:"", date:"", authors:"", notes:(), institutions:"", header-slide:BB-header_slide) = {
let a = {if outline == true{1} else {0}}
v((1-a)*5em)
align(center+horizon)[
#set text(weight: 700, 2em)
// #line(length:100%, stroke:3pt+default_color)
#box(stroke: (bottom: 4pt+ color, top:0pt, left:0pt, right:0pt),outset:(bottom:.5em))[#text(fill:color)[#title]]
// #line(length:100%, stroke:3pt+default_color)
#if title_notes !=none {footnote[#title_notes]}
#v(1em, weak: true)
#set text(weight: 500, 0.1em)
]
let author_note = authors.zip(notes)
pad(
top: 0.1em,
bottom: 0.1em,
x: 2em,
grid(
columns: (1fr,) * calc.min(3, authors.len()),
gutter: 1em,
..authors.map(author => align(center,
text(weight: 700, .8em, author)
)),
..institutions.map(institutions => align(center, text(weight: 700, .8em, institutions)))
),
)
[#align(center)[#text(size:0.6em)[#date]]]
}
//スライドのデザイン，タイトルスライドのデザイン，フッターのデザインをまとめる．
#let BB-page-setter(footer:"",body) = {
set page(fill: rgb("2f4f4f"),footer: [#set text(10pt);#footer])
set text(fill: rgb("f5f5f5"))
body
}
//スライドのデザイン，タイトルスライドのデザイン，フッターのデザインをまとめる．
#let BlackBoard = (slide_theme:BB-header_slide, title_theme:BB-title_slide, page_theme: BB-page-setter,default-color: yellow.lighten(50%),emph-color:eastern.darken(40%))
//------
//--------Simpleのテーマ
//Headerスライドのデザイン
#let Simple-header_slide(title,now:0, end:0,color:"", tcolor:"", current-headings: "", outline: false) = {
set text(size: 23pt, weight:700)
let a = {if outline == true{1} else {0}}
if outline == true {pad(top:30pt,bottom:-30pt)[
#heading-outline(color:color, current-headings: current-headings)]
v(-13pt)
}
pad(left: -20pt, top:30pt)[
#if title == [] { v(20pt) }else { h(20pt);text(size:1.2em)[#title]; h(1fr); text(size:0.7em)[#now/#end]; v(-15pt) }
#line(
length: 30cm,
stroke: 4pt + tcolor.lighten(80%),
) #v(a*2.5em)
]
}
//タイトルスライドのデザイン
#let Simple-title_slide(now:"",end:"", color:"",tcolor:"", outline:"", title:"", title_notes:"", date:"", authors:"", notes:(), institutions:"", header-slide:BB-header_slide) = {
align(center+horizon)[
#set text(weight: 700, 2em)
// #line(length:100%, stroke:3pt+default_color)
#box(stroke: (bottom: 8pt+ color, top:0pt, left:0pt, right:0pt),outset:(bottom:.5em))[#text(fill:color)[#title]]
// #line(length:100%, stroke:3pt+default_color)
#if title_notes !=none {footnote[#title_notes]}
#v(1em, weak: true)
#set text(weight: 500, 0.1em)
]
let author_note = authors.zip(notes)
pad(
top: 0.1em,
bottom: 0.1em,
x: 2em,
grid(
columns: (1fr,) * calc.min(3, authors.len()),
gutter: 1em,
..authors.map(author => align(center,
text(weight: 700, .8em, author)
)),
..institutions.map(institutions => align(center, text(weight: 700, .8em, institutions)))
),
)
[#align(center)[#text(size:0.6em)[#date]]]
}
//スライドのデザイン，タイトルスライドのデザイン，フッターのデザインをまとめる．
#let Simple-page-setter(footer:"",body) = {
set page(fill: white,footer: [#set text(10pt);#footer])
set text(fill: black)
body
}
//スライドのデザイン，タイトルスライドのデザイン，フッターのデザインをまとめる．
#let Simple = (slide_theme:Simple-header_slide, title_theme:Simple-title_slide, page_theme: Simple-page-setter, default-color: gray.darken(30%),emph-color:white)
//------
//--------Tropicalのテーマ
//Headerスライドのデザイン
#let Tropical-header_slide(title,now:0, end:0,color:"", tcolor:"", current-headings: "", outline: false) = {
set text(size: 23pt, weight:700)
let a = {if outline == true{1} else {0}}
if outline == true {pad(top:30pt,bottom:-30pt)[
#heading-outline(color:gradient.linear(yellow, red, angle: 0deg), current-headings: current-headings)]
v(-13pt)
}
pad(left: -20pt, top:30pt)[
#h(20pt);#box(fill:gradient.linear(red, red.darken(30%), angle: 90deg),outset:(bottom:10pt, left:20pt,top:5pt), radius: (
left: 5pt,
top-right: 20pt,
))[#text(size:1.2em,fill:white)[#title] #hide[あ]]; #h(1fr); #text(size:0.7em,fill:black)[#now/#end]; #v(-15pt)
#line(
length: 30cm,
stroke: 4pt +red.darken(30%),
) #v(a*2.5em)
]
}
//タイトルスライドのデザイン
#let Tropical-title_slide(now:0,end:0, color:"",tcolor:"", outline:"", title:"", title_notes:"", date:"", authors:"", notes:(), institutions:"", header-slide:BB-header_slide) = {
let a = {if outline == true{1} else {0}}
v((1-a)*5em)
align(center+horizon)[
#set text(weight: 700, 2em, fill:white)
// #line(length:100%, stroke:3pt+default_color)
#box(stroke: (bottom: 8pt, top:0pt, left:0pt, right:0pt),outset:(bottom:.5em))[#text(fill:white)[#title]]
// #line(length:100%, stroke:3pt+default_color)
#if title_notes !=none {footnote[#title_notes]}
#v(1em, weak: true)
#set text(weight: 500, 0.1em)
]
let author_note = authors.zip(notes)
pad(
top: 0.1em,
bottom: 0.1em,
x: 2em,
grid(
columns: (1fr,) * calc.min(3, authors.len()),
gutter: 1em,
..authors.map(author => align(center,
text(weight: 700, .8em, author)
)),
..institutions.map(institutions => align(center, text(weight: 700, .8em, institutions)))
),
)
[#align(center)[#text(size:0.6em)[#date]]]
}
//スライドのデザイン，タイトルスライドのデザイン，フッターのデザインをまとめる．
#let Tropical-page-setter(footer:"",body) = {
set page(fill:gradient.linear(rgb("00008b"), yellow.darken(30%), angle: 0deg),footer: [#set text(10pt);#footer])
set text(fill: rgb("f5f5f5"))
body
}
//スライドのデザイン，タイトルスライドのデザイン，フッターのデザインをまとめる．
#let Tropical = (slide_theme:Tropical-header_slide, title_theme:Tropical-title_slide, page_theme: Tropical-page-setter,default-color: yellow.darken(40%),emph-color:white)
//------ |
|
https://github.com/arthurcadore/typst-intelbras | https://raw.githubusercontent.com/arthurcadore/typst-intelbras/main/README.md | markdown | MIT License | # Template Typst - Intelbras
#### This repository is dedicated to Typst's Template for Intelbras Reports.
---
### Getting Started:
This repository is configured to work with devcontainers on GitHub, using a `.devcontainer` configuration to automatically install all necessary packages for compiling `.typ` files.
To get started, create a new codespace on the main branch. If you encounter any issues, you can refer to [This tutorial](https://docs.github.com/en/codespaces/getting-started/quickstart)
If you prefer to use it on your local machine, ensure that the following packages are installed:
- Git version 2.34.1
- Typst v0.11.0 ([Instalation Tutorial](https://github.com/typst/typst))
### Using Typst Compiler:
Once Typst is installed, you can create a new file with a `.typ` extension, similar to the files located in `./examples/.` The file should import the following content in its header to work properly:
```
#import "../templates/support-en.typ": *
#import "@preview/codelst:2.0.1": sourcecode
#show heading: set block(below: 1.5em)
#show par: set block(spacing: 1.5em)
#show: doc => support(
title: "API Test Report Intelbras",
subtitle: "Network Technician Support Analyst",
authors: "<NAME>",
date: "May, 02, 2023",
doc,
)
// WRITE YOUR CUSTOM FILE CONTENT BELOW USING TYPST SINTAX.
```
While creating the file, you can save it using `Ctrl + S`, and the extension (pre-installed in the devcontainer only) will automatically compile the code and create a `.pdf` file!
If you are using this repository on your local machine, ensure that VSCode has the following extensions installed for proper functionality:
- nvarner.typst-lsp
- mathematic.vscode-pdf
Optional extensions (Preinstalled in devcontainer):
- dracula-theme.theme-dracula
- GitHub.copilot
### References Used:
- [Typst IFSC Templates - Gabrielluizep](https://github.com/gabrielluizep/typst-ifsc)
- [Typst Instalation](https://github.com/typst)
- [Typst Documentation](https://typst.app/docs/)
|
https://github.com/thornoar/typst-libraries | https://raw.githubusercontent.com/thornoar/typst-libraries/master/common.typ | typst | // Positioning
#let centering(shallow: true, content) = {
if shallow { stack(dir: ltr, spacing: 1fr, [], content, []) } else { align(center)[ #content ] }
}
#let mfrac(a, b) = move(a, dy: -0.2em) + "/" + move(b, dy: 0.2em, dx: -0.1em)
#let vphantom(size) = box(height: size, width: 0pt, [])
#let hphantom(size) = box(height: 0pt, width: size, [])
// Colors
#let palered = rgb("#ffc0c0")
#let palegreen = rgb("#c0ffc0")
#let paleblue = rgb("#c0c0ff")
#let paleyellow = rgb("#ffffc0")
#let palemagenta = rgb("#ffc0ff")
#let palecyan = rgb("#c0ffff")
#let palegray = rgb("#f3f3f3")
// Math
#let circ = math.circle.stroked.tiny
#let hs = h(5pt)
#let lle = math.lt.eq.slant
#let gge = math.gt.eq.slant
|
|
https://github.com/kochetov-dmitrij/personal-page | https://raw.githubusercontent.com/kochetov-dmitrij/personal-page/main/cv/pdf/README.md | markdown | # Bare-bones Typst CV
To generate `main.pdf` and watch for live changes, run:
```bash
make watch
```
To publish `main.pdf` to the server, run:
```bash
make release OUTPUT=dmitrii_kochetov_en1.pdf
```
|
|
https://github.com/maantjemol/Aantekeningen-Jaar-2 | https://raw.githubusercontent.com/maantjemol/Aantekeningen-Jaar-2/main/Security/samenvatting.typ | typst | // Update this import to where you put the `lapreprint.typ` file
// It should probably be in the same folder
#import "../template/lapreprint.typ": template
#import "../template/frontmatter.typ": loadFrontmatter
#import "@preview/drafting:0.2.0": *
#import "@preview/cetz:0.2.2"
#let default-rect(stroke: none, fill: none, width: 0pt, content) = {
pad(left:width*(1 - marginRatio), rect(width: width*marginRatio, stroke: stroke)[
#content
])
}
#let defaultColor = rgb("#f2542d")
#let caution-rect = rect.with(inset: 1em, radius: 0.5em, fill: defaultColor.lighten(96%), width:100%)
#let note = (content) => inline-note(rect: caution-rect)[#content]
#show: template.with(
title: "Security",
subtitle: "Samenvatting",
short-title: "IBIA Samenvatting",
venue: [ar#text(fill: red.darken(20%))[X]iv],
// This is relative to the template file
// When importing normally, you should be able to use it relative to this file.
theme: defaultColor,
authors: (
(
name: "<NAME> . ",
),
),
kind: "Samenvatting",
abstract: (
(title: "Samenvatting", content: [#lorem(100)]),
),
open-access: true,
margin: (
(
title: "",
content: [
],
),
),
font-face: "Open Sans"
)
#set page(
margin: (left: 2in, right: 0.8in), paper: "us-letter"
)
#let marginRatio = 0.8
#let default-rect(stroke: none, fill: none, width: 0pt, content) = {
pad(left:width*(1 - marginRatio), rect(width: width*marginRatio, stroke: stroke)[
#content
])
}
#set-page-properties()
#show terms: it => [
#note[#text(defaultColor, weight: 600, size: 10pt)[#it.children.first().term]\ #it.children.first().description]
]
#set heading(numbering: none)
#show heading: set text(defaultColor, weight: "medium")
= Introduction to Information Security
Three important security principles are:
+ Confidentiality: Only authorized users should be able to access data.
+ Integrity: Data should not be altered by unauthorized users.
+ Availability: Data should be available when needed.
== AAAA properties:
+ Authenticity: The identity of the user should be verified.
+ Authorization: The user should have the necessary permissions.
+ Accuracy: The data should be accurate.
+ Accountability: The user should be accountable for their actions. (logs)
== STRIDE:
+ Spoofing: Pretending to be someone else.
+ Tampering: Altering data.
+ Repudiation: Denying an action.
+ Information Disclosure: Unauthorized access.
+ Denial of Service: Preventing access.
+ Elevation of Privilege: Gaining unauthorized access.
*Stride steps*
+ Define the key assets and security requirements for the system
+ Design data flow diagram(s) for the system
+ Draw trust boundaries
+ Identify threats
+ Mitigate threats with controls
+ Validate that threats were mitigated
== Successful attack:
+ System susceptibility: Vulnerability
+ Threat accessibility: Attack surface
+ Threat capability: recourses, tools, knowledge
== Why is security hard?
+ Complexity: More complex systems are harder to secure.
+ Afterthought: Security is often added after the fact.
+ Benefits are evident best after a failure
Security is needed to prevent and counteract the unwanted consequences
== Trade-offs:
+ Security vs. Usability
+ Security unaware users want security
+ Security has cost, but becomes only a direct gain when a failure occurs
+ Failure can cost less than prevention
+ Algo is secure but the implementation is not
+ Practical security is ofter weaker than theoretical security
+ Complexity increases the attack surface
= Risk management:
== Enterprise Risk Management:
+ Identify risks
+ Evaluate risks
+ Mitigate risks
+ Monitor risks
+ Review risks
== Risk assessment:
+ Assess risk and determine need
+ Implement policy and controls
+ Promote awareness
+ Monitor and evaluate
= Principles, Best Practices and Standards
== Design principles:
- Separation of duties: No single person should have all the power
- Least privilege: Only the necessary permissions
== Standards and best practices:
- ISO/IEC 27001: Information Security Management System
- NIST: National Institute of Standards and Technology
- ANSI: American National Standards Institute
= Network security:
== OSI model: 7 layers
+ Physical: Fiber, copper
+ Data link: Ethernet, switch, bridge
+ Network: IP, ICMP, ARP
+ Transport: TCP, UDP
+ Session: API, sockets
+ Presentation: FTP, SSL, IMAP
+ Application: HTTP, DNS, SMTP
/ Fragmentation: Splitting data into smaller parts
== Network layer:
- *IPsec:* Security protocols used in VPNs
- *Authentication header:* a header that shows that the data hasn't been tampered with
- *ESP header:* does more that AH, also encrypts the data and authenticates it.
- *IKE:* a protocol used to establish a secure connection, a handshake
- *ICMP redirect attack:* router can redirect with ICMP packets. Attacker can forge these packets to redirect to their own machine.
== Transport layer:
- *TCP three way handshake:* SYN (ask server), SYN-ACK (server ack, asks client), ACK (client ack)
- *SYN Flooding Attack:* DoS with SYN packets
== Presentation:
- *SSH:* Secure Shell, encrypted terminal. Steps:
+ Client initiates connection
+ Server sends public key
+ Negotiate encryption
+ Open session
== Application layer:
- *DNS:* Domain Name System, translates domain names to IP addresses
- *DNS poisoning:* Changing DNS records to redirect traffic to a malicious server
== Firewalls:
A firewall can perform a few actions based on the rules:
- Allow: Allow the packet
- Reject: Block the packet, inform
- Drop: Silently discard the packet
#figure(
caption: "Firewall",
)[#image("./images/firewall.png", width: 100%)]
*Proxy firewalls:* Inspects packets and can block based on content. Can do more intelligent filtering.
== Intrusion Detection Systems:
An intrusion detection system collects events, processes them and alerts when something is wrong. You can source the data from:
- Network: Network-based IDS (packet sniffing)
- Host: Host-based IDS (logs)
#pagebreak()
= Bayes' theorem:
$ P(A|B) = (P(B|A) P(A)) / P(B) $
- Left side of equation $P(A|B)$
- Probability of event $A$ given another event $B$ (This situation is also called posterior outcome)
- Signifies the updated probability of $A$, when a new evidence / event $B$ occurs
- Right side of equation: (how it happens)
- $P(A)$ = Probability of event $A$ if there is no event $B$ (This situation is also called prior outcome)
- $P(B)$ = marginal likelihood. (probability of observing new event $B$ )
- $P(B|A)$ = The likelihood of $B$ when event $A$ is present
At its simplest, Bayes' Theorem takes a test result and relates it to the conditional probability of that test result given other related events. For high-probability false positives, the theorem gives a more reasoned likelihood of a particular outcome.
*Event analysis:*
- Signature-based: Known patterns, fast, but can't detect new attacks
- Anomaly-based IDS: Detects deviations from normal behavior (failed login attempts, total files deleted, etc.), can detect new attacks but hard
== IPS:
An intrusion prevention system is like an IDS but can also take action. It can:
- IPS augmenting firewall: alter packets, strip out malware, terminate connections
- in-host IPS: terminate processes
= Application security:
The *stack* and the *heap* are two memory areas in a program. The stack is used for function calls and the heap for dynamic memory allocation. The stack is faster but limited in size.
== Stack:
- Calling function main:
+ Push arguments of func in reverse order on the stack
+ Push the return address where main wants to get back
+ Jump to the func address
- Called function func:
+ Push the current (main’s) frame pointer to the stack
+ Set new %ebp to the current %esp (where the stack ends now)
+ Push local variables on the stack
- Return to main:
+ Reset the stack frame: %esp = %ebp, %ebp = (%ebp)
+ Jump back to the planned return address: %eip = 4(%esp)
- *%EBP:* base pointer, points to the base of the current stack frame
- *%ESP:* stack pointer, points to the top of the stack
- *%EIP:* instruction pointer, points to the next instruction to execute
== Buffer overflow:
A buffer overflow is when a program writes more data to a buffer than it can hold. This can overwrite the return address %EBP. This can be used to execute arbitrary code. You can also inject shellcode and point %EIP to it.
We can use *NOP* instructions to slide to the shellcode. This is called a *NOP sled*.
== Heap overflow:
A heap overflow is when a program writes more data to the heap than it can hold. This can overwrite the heap metadata and corrupt the heap. This can be used to execute arbitrary code. *Malloc* and *free* are common functions that can be exploited.
== Heartbleed:
Heartbleed is a vulnerability in OpenSSL that allows an attacker to read memory from the server. This can include private keys, passwords, etc.
#figure(
caption: "Heartbleed",
)[#image("./images/heartbleed.png", width: 100%)]
== String formatting:
String formatting is when a program uses a format string to print data. If the format string is user-controlled, an attacker can read and write memory.
== Race conditions:
Modify data between the check and the use. This can be done with multiple threads or processes.
== Prevention techniques:
+ Memory safety: all its possible executions are memory safe. Things like Rust, GO and Java are memory safe.
+ Spatial Safety: check if you are writing to the correct memory
+ Temporal Safety: A temporal safety violation occurs when trying to access undefined memory
Spatial safety ensures access is to a legal region Temporal safety ensures it is still allocated and initialized (still valid)
== Type safety:
Type safety ensures that operations on the object are always compatible with its type.
#pagebreak()
== Avoiding exploitation:
- Make the exploitation steps more difficult or impossible
- Avoid bugs via secure coding and better code audit
Fix the architecture:
- Use a language that is memory safe
- Implement security checks
make stack and heap non-executable, so that the
architecture will not support running anything there (non-code memory region).
== Stack Canaries:
A stack canary is a random value placed before the return address. If the canary is overwritten, the program will exit. This can prevent buffer overflows.
== ASLR:
Address Space Layout Randomization is a technique that places standard libraries and other useful
elements in memory. This makes it harder for an attacker to predict where things are.
== How can we detect an ongoing attack?:
If we observe that a program deviates from its expected
behavior, then it might be compromised.
We can build a CFG to see if the program deviates from its normal flow. We can then monitor the program and see if it deviates from the CFG. This can be done by inserting labels in the code just before the target address of an indirect transfer. _indirect calls_ will then be checked against the CFG.
/ In-line Reference Monitor: #text[
This is how we can detect an ongoing attack:
+ insert a label just before the target address of an indirect transfer
+ insert code to check the label of the target at each indirect transfer
+ stop execution if labels don’t match
We can use detailed labeling to check if we aren't reusing code that should not be reused.
]
= Symmetric Cryptography:
The goals of cryptography are:
- Confidentiality: Only authorized users can read the data
- Authentication: Verify the identity of the sender
- Non-repudiation = assuring that actions or commitments in the past cannot be denied
There are a few different classifications for cryptographic algorithms:
- *Symmetric:* Same key for encryption and decryption, mainly used for *confidentiality*
- *Public-key cryptography:* Different keys for encryption and decryption, mainly used for *authentication* and *non-repudiation*
- *Hash functions:* Used for *authentication*
Symmetric encryption uses the same key for encryption and decryption. The key should be kept secret. An example is a *caesar cipher* (rot13).
There are a few different techniques for symmetric encryption:
- *Substitution:* replace each letter with another
- *Diffusion*: replace the order of the letters
- *Using a key:* use a key to encrypt the data, the method is known but the key is secret
== Stream ciphers:
Stream ciphers encrypt one bit at a time. They work like this:
- Generate a key stream
- XOR the key stream with the plaintext
- XOR the key stream with the ciphertext to decrypt
/ The one-time pad: #text[
The one-time pad is a stream cipher that uses a key as long as the plaintext. This is unbreakable if the key is truly random and only used once. It's not practical because the key needs to be as long as the plaintext.
When the key is reused, the one-time pad is no longer secure. This is called the *key reuse problem*.
]
== Block Ciphers
Block ciphers encrypt a block of data at a time. They use a fixed block size. An example is the *Data Encryption Standard* (DES).
== DES:
DES is a block cipher that uses a 56-bit key. It uses a 64-bit block size. It uses a Feistel network with 16 rounds. DES is no longer considered secure because the key is too short.
/ 2DES meet-in-the-middle attack: The DES algorithm can be used twice with two different keys. When you have the plaintext and the ciphertext, you can use a meet-in-the-middle attack to find the key. You can encrypt the plaintext with all possible keys and decrypt the ciphertext with all possible keys. You can then compare the results to find the keys.
== AES:
The Advanced Encryption Standard is a block cipher that uses a 128-bit block size. It uses a 128, 192 or 256-bit key. It uses a substitution-permutation network with 10, 12 or 14 rounds.
#pagebreak()
== Modes:
A mode is a way to use divide the plaintext into blocks and encrypt them. The ECB mode encrypts each block separately. This is not secure because identical blocks will have identical ciphertext. The CBC mode uses an IV (Initialization vector) to XOR the plaintext before encryption. Often the IV is the previous ciphertext block. CTR mode uses a counter to generate a key stream. This is parallelizable and less prone to errors.
== Hash functions:
Hash functions take an input and produce a fixed-size output. They are used for integrity and authentication.
Hash functions should have a few properties:
- Deterministic: The same input should always produce the same output
- Fast: The hash should be fast to compute
- Pre-image resistance: It should be hard to find the input for a given hash
- Second pre-image resistance: It should be hard to find a different input for the same hash
- Collision resistance: It should be hard to find two inputs that produce the same hash
Hash functions without a secret key are used to assure data integrity. They allow to detect changes in the transmitted messages.
Hash functions can also be used for authentication (of data). In this case, a secret key is used, together with the message, and we call the function a Message Authentication Code (*MAC*).
/ Mac: #text[
A MAC is a hash function that uses a secret key. It can be used to verify the integrity of a message. The key should be kept secret.
Commonly used MACs are:
- HMAC: Hash-based MAC
- CMAC: Cipher-based MAC
]
= Asymmetric Cryptography:
The idea is that everyone can encrypt a message with a public key, but only the person with the private key can decrypt it. This is used for authentication and non-repudiation.
#pagebreak()
== Diffie-Hellman:
*Agree on Public Values:*\
Alice and Bob publicly agree on two mathematical values:
- A large prime number (p) - This acts like a base number for calculations.
- A primitive root of p (g) - A special number that has specific mathematical properties with respect to p.
*Private Key Generation:*
- Alice: Chooses a random secret number (a) and keeps it private.
- Bob: Chooses a random secret number (b) and keeps it private.
*Key Exchange (Public Communication):*
- Alice: Calculates $A = g^a (mod p)$ and sends this value publicly to Bob.
- Bob: Calculates $B = g^b (mod p)$ and sends this value publicly to Alice.
*Shared Secret Key Derivation (Private Calculation):*
- Alice: Calculates the shared secret key using Bob's public value (B) and her private key (a): S = B^a (mod p).
- Bob: Calculates the same shared secret key using Alice's public value (A) and his private key (b): $S = A^b (mod p)$.
To prevent a MITM attack, Alice and Bob need to perform
mutual authentication.
== Digital signature:
A digital signature is a way to verify the authenticity of a message. It uses a private key to sign the message and a public key to verify the signature.
You as a sender can sign a message with your private key. The receiver can then verify the signature with your public key. This way, the receiver knows that the message is from you. Algorithms like *RSA* can be used for this.
== How can we be sure that a public key belongs to a certain entity?
We can use a *Certificate Authority* (CA) to verify the identity of the entity. The CA signs the public key with its private key. The receiver can then verify the signature with the CA's public key. The CA is a trusted third party (TTP) that is trusted by the owner of the
public key as well as other entities that use the public key.
== Public-key encryption/decryption:
The sender can encrypt a message with the receiver's public key. The receiver can then decrypt the message with their private key. This way, only the receiver can read the message. Algorithms like *RSA* can be used for this.
Public-key algorithms require more computation time and are therefore slower than symmetric-key algorithms.
== *Digital signatures vs. public-key encryption:*
- Digital signatures are used to verify the authenticity of a message.
- *only the sender can sign, everyone can verify*
- Public-key encryption using public-key cryptography is used to encrypt a message.
- *only the receiver can decrypt, everyone can encrypt*
#pagebreak()
== Post-quantum cryptography:
Shor’s algorithm allows to calculate discrete logarithms or to do integer
factorization in polynomial time. This means that RSA and ECC are no longer secure. Post-quantum cryptography investigates how we can implement crypto after/if quantum computers become ubiquitous.
== SSL-TLS:
- SSL and TLS are protocols that provide secure communication over the internet. They use a combination of symmetric and asymmetric encryption.
- The handshake is used to establish a secure connection.
- The server sends its certificate to the client.
- The client verifies the certificate with the CA.
- The client then generates a pre-master secret and sends it to the server.
- The server and client then generate the master secret from the pre-master secret.
- They then use the master secret to generate the session keys.
= Web security:
== SQL injection:
SQL injection is when an attacker injects SQL code into a query. This can be used to read or write data. You can prevent this by using prepared statements or by escaping user input.
```sql
e@m' OR 1=1); --
```
You can prevent this by verifying the input and using prepared statements. Delete suspicious characters. Replace problematic characters with safe ones:
- `’` $->$ `\’`
- `"` $->$ `\"`
- `;` $->$ `\;`
- `-` $->$ `\-`
Limit server privileges on the database and encrypt sensitive data.
== Maintaining state:
HTTP is stateless. You can use cookies or sessions to maintain state. Cookies are stored on the client side and sessions are stored on the server side. Another way to maintain state is to use hidden fields in forms. This is prone to tampering.
*Cookies:*
- Cookies are stored on the client side
- They can be used to store session information
- They can be used to track users
- A stolen cookie can be used to *hijack a session*
== Session Hijacking:
Holder of a session cookie can access the site with the privileges of an authenticated user. This can be done by stealing the session cookie.
#pagebreak()
You can get these cookies by:
- Sniffing the network (HTTPS)
- Compromising the server or the client (harden machines)
- Predicting the cookies (use random session IDs)
- Redirect the user to a malicious site (mark cookies as secure)
From the server side, you can:
- Set sensitive cookies to be very short-lived
- Invalidate the cookie when the user logs-out
- Make cookies different from session to session
== CSRF
Cross-Site Request Forgery is when an attacker tricks a user into performing actions on a different site. This can be done by sending a link to the user. The goal is to issue a request to the server via the user’s browser.
*Protections:*
- The browser will set the REFERER field indicating the page that hosted the clicked link.
- Adding a secret token to the form that is not known to the attacker.
== Client-side:
Browsers can execute JavaScript. This can be used to manipulate the DOM. This can be used to steal cookies or to perform actions on behalf of the user.
*XSS* is an attack where an attacker injects JavaScript into a page. This can be used to steal cookies or to perform actions on behalf of the user.
/ Same Origin Policy: #text[
The same-origin policy is a security measure that prevents a script from one site from accessing data on another site. This is to prevent cross-site scripting attacks.
]
== Cookies vs Tokens:
Cookies are:
- Stored on the client side
- Sent with every request
- Can be stolen with XSS
- Better when we need (backwards) compatibility
Tokens are:
- Client stores and transmits the user’s claims and info
- Better for stateless client-server communications
- Better when cross-domain and cross-origin requests need to be enabled
#pagebreak()
== Tracking:
There are a few ways to track users:
- Cookies: stored on the client side
- Browser fingerprinting (user-agent, screen size, etc.)
- Information (identity) trackers: (phone number, email, etc.)
- Tracking scripts (Google Analytics, etc.)
== Other web security issues:
- Command injection: when an attacker injects commands into a system
- Directory traversal: when an attacker can access files outside of the web root
- File inclusion: when an attacker can include files from the server
- File upload: when an attacker can upload files to the server
= Secure software development:
== Principles:
- Least privilege: Only give the necessary permissions
- Verify input: Always verify input
- Use Safe Functions: Use safe functions like prepared statements
- Use safe libraries: Use libraries that are secure
== Code reviews
Code reviews are a way to find bugs and vulnerabilities in the code. They can be done manually or automatically. Examples:
- Pull request reviews
- Pair programming
- Over the shoulder reviews
- Tool assisted reviews
- etc...
= Mobile security:
== API levels:
Android often releases new versions of the OS. These have new features, ans new API levels. Apps specify there minimum and target api.
== Apps:
Apps have no single entry point or main function. Users interact with the GUI, the app interacts with the system APIs. These APIs are often event driven. An app consists of a few different components:
- *Activities:* A screen with a user interface
- *Service:* A background process
- *Content provider:* A way to share data between apps, database interface
- *Broadcast receiver:* receiver/dispatcher for _Intent_ messages
All components can interact asynchronously through _Intents_. Intents can be explicit or implicit. Implicit intents are resolved by the system. App A may declare that it can handle actions (intents)
of certain types. When another app wants to make this action (sends
the implicit intent), the system will know it can count
on A. The user may be offered to choose from a set of apps
(including A). Think of opening a google maps url in the browser or google maps.
/ APK files: Apps are distributed as APK files. These are zip files with a specific structure. They contain the compiled code, resources, and a manifest file. The manifest file contains metadata about the app. These files are signed with a certificate.
== Permissions:
There are a few different types of permissions:\
*Install-time permissions*:
- Normal permissions: These are granted automatically (_internet access_)
- signature: granted to trusted packages (_system apps_)
*Run-time permissions:*
- dangerous— granted if the user approves at run-time (_notifications_)
*Special permissions:*
- granted by the user in the settings (_install unknown apps_)
*Issues with permissions:*
- Confused deputy attack: when an app uses permissions from another app
- Request more permissions than needed
- Users do not understand permissions
- Permissions evolve over time, which makes them confusing.
/ Advertising ID: The advertising ID is an alternative for the IMEI. It is used for advertising purposes. It can be reset by the user. It is used to track users across apps.
A lot of vulnerabilities come from interactions among apps.
== Mobile malware:
- Rooting device
- Making premium SMS/calls
- Turning phone into bot
- Stealing private information
- Adware and click fraud
- Hindering usage: hijacking screens, redirecting, installing more apps
- Ransomware
- Cryptojacking
*Detecting malware* can be done by using _static_ or _dynamic_ analysis. Static analysis is when you analyze the code without running it. Dynamic analysis is when you run the code and analyze the behavior.
#pagebreak()
= Access Control:
== Controlling access on a system:
- *Identification:* Who are you?
- *Authentication:* Prove it
- *Authorization:* What can you do?
- *Accountability:* What did you do?
== Identity management system:
An *identity management system* is a system that manages the identity of users. It can be used to manage access to resources. It can be used to manage user accounts, roles, and permissions.
- Can be tricky for large organizations
- Various security requirements:
- Privacy/anonymity/full transparency
- Strong link to physical identity
- Revocability
Identity based authentication links 3 entities:
- *User:* a physical person or machine
- *Identity:* entry in an IMS to which a user can be associated
- *Subject:* A binary or a shell script that can run
/ Audit: #text[
An audit reviews the records of the system to check compliance with the security policy. It can be done by an internal or external auditor. It can be done manually or automatically.
]
*Access control policy:* A policy that defines who can access what. It can be based on roles, attributes, or other factors.
== Access control policies:
- *DAC:* Discretionary Access Control, the owner decides who can access the resource. _You can manage your own social media. but noy others_
- *MAC:* Mandatory Access Control, the system decides who can access the resource. _Military security, organization wide policies_
- *NAC:* Non-Discretionary Access Control, _admin decides who can access resources_
- *RBAC:* Role-Based Access Control, access is based on roles. roles have access to objects, users have roles. _HR can access HR data, have HR role_
- *ABAC:* Attribute-Based Access Control, access is based on attributes. _Only users with a certain clearance can access the data_
#pagebreak()
== Access Control Lists (ACLs) vs. Capabilities:
*ACLs:* Access Control Lists are lists that define who can access a resource. They can be attached to the resource or the user. *Capabilities* are rules that define what a user can do. They can be attached to the user or the resource.
#figure(caption: "Access Control Matrix",)[#image("./images/acm.png", width: 100%)]
An *Access Control Matrix* is a way to represent who can access what. It can be used to define access control policies.
== Access Control Privileges in computer systems:
*Subject classes:*
- *Owner:* the creator/owner of the object
- *Group:* a group of users with the same permissions
- *World:* least privileged users
*Privileges:*
- *Read:* (r) read the object
- *Write:* (w) write to the object
- *Execute:* (x) execute the object
== Separation of Duties:
Separation of duties is a security principle that states that no single person should have all the power. It can be used to prevent fraud and errors. It can be used to prevent conflicts of interest.
/ Example: At least 2 professors evaluate a bachelor thesis; a student cannot be a student assistant in a course they take.
#pagebreak()
== Multi-level Security Policies:
- *The Bell-La Padula Model:* A model that defines how information can flow in a system. It has two rules: the simple security rule (no subject may read data from a higher level) and the \*-property rule (no subject may write data to a lower level).
- *Biba model:* Data may be visible to many users, but can only be modified by a user with the right clearance. Has two rules: the simple integrity rule (no subject may write data to a higher level) and the \*-integrity rule (no subject may read data from a lower level). _Everyone can read a website, but only admins can edit it_
- *Chinese wall model:* A model that prevents conflicts of interest. It prevents a user from accessing data that could create a conflict of interest. _A lawyer cannot work for two competing companies_
|
|
https://github.com/typst-community/mantodea | https://raw.githubusercontent.com/typst-community/mantodea/main/src/lib.typ | typst | MIT License | #import "_pkg.typ"
#import "_valid.typ"
#import "author.typ"
#import "component.typ"
#import "example.typ"
#import "link.typ"
#import "theme.typ"
#import "style.typ"
#import "util.typ"
#let _version = version
/// The main template function, this returns a function which is used in a
/// `show`-all rule.
///
/// - title (str, content): The title for of this document.
/// - subtitle (str, content, none): A subtitle shown below the title.
/// - authors (str, content, array): The authors of the document.
/// - urls (str, array, none): One or more URLs relevant to this document.
/// - version (str, version): The version of this document. A string can be
/// passed explicitly to avoid the automatic `v` prefix.
/// - date (datetime): The date at which this document was created.
/// - abstract (str, content, none): An abstract outlining the purpose and
/// contents of this document.
/// - license (str, content, none): The license of this document or a related
/// piece of intellectual property.
/// - theme (theme): The theme to use for this document.
/// -> function
#let mantodea(
title: [Title],
subtitle: none,
authors: "<NAME> <<EMAIL>>",
urls: none,
date: datetime(year: 1970, month: 1, day: 1),
version: version(0, 1, 0),
abstract: lorem(100),
license: "MIT",
theme: theme.default,
_validate: true,
) = body => {
if _validate {
import _valid as z
z.parse(title, z.content(), scope: ("title",))
z.parse(subtitle, z.content(optional: true), scope: ("subtitle",))
z.parse(abstract, z.content(optional: true), scope: ("abstract",))
z.parse(license, z.content(optional: true), scope: ("license",))
z.parse(theme, _theme.schema, scope: ("theme",))
authors = z.parse(
z.array(z.string(), min: 1, pre-transform: z.coerce.array),
authors,
scope: ("authors",),
)
urls = z.parse(
urls,
z.array(
z.string(),
pre-transform: z.coerce.array,
post-transform: (self, it) => if it == (none,) { none } else { it },
optional: true,
),
scope: ("urls",),
)
_pkg.t4t.assert.any-type(_version, version)
} else {
authors = if type(authors) == str { (authors,) } else { authors }
urls = if type(urls) == str { (urls,) } else { urls }
}
set document(title: title, author: authors)
show: style.default(theme: theme, _validate: false)
component.make-title-page(
title: title,
subtitle: subtitle,
authors: authors,
urls: urls,
version: version,
date: date,
abstract: abstract,
license: license,
theme: theme,
_validate: false,
)
component.make-table-of-contents(
title: heading(outlined: false, numbering: none, level: 2)[Table of Contents],
columns: 1,
theme: theme,
_validate: false,
)
body
}
|
https://github.com/Error-418-SWE/Documenti | https://raw.githubusercontent.com/Error-418-SWE/Documenti/src/3%20-%20PB/Documentazione%20interna/Verbali/24-03-06/24-03-06.typ | typst | #import "/template.typ": *
#show: project.with(
date: "06/03/24",
subTitle: "Meeting post colloquio con Committente",
docType: "verbale",
authors: (
"<NAME>",
),
missingMembers: (
"<NAME>",
),
timeStart: "09:00",
timeEnd: "10:00",
);
= Ordine del giorno
A seguito dell'incontro con il #cardin, il gruppo ha svolto un meeting interno riguardante:
- Considerazioni scaturite dal colloquio con il #cardin\;
- Pianificazione.
== Considerazioni scaturite dal colloquio con il #cardin
Il gruppo ha discusso i diversi argomenti trattati con il #cardin durante il meeting.
=== Database
Il gruppo ha deciso di scegliere la linea di progettazione che vede il database come parte del capitolato, e in particolare come data layer del software. Come suggerito dal #cardin l'accesso avviene tramite backend anziché tramite browser visti i potenziali problemi di sicurezza che questo comporterebbe.\
La scelta è stata conseguita in seguito ai consigli del #cardin, che ha anche portato l'esempio del pattern CQRS come caso di design dove un database viene usato per sola lettura, come nel caso di WMS3. Il gruppo sceglie però di non implementare questo pattern, dato che nel suo schema è presente una parte dedicata alla scrittura dei dati che non è oggetto del capitolato.
=== Classi anemiche
Il gruppo ha deciso di proseguire con l'implementazione di classi che rappresentano le istanze del database.
Il dubbio sull'implementarle o meno, poiché quest'ultime sono prive di comportamento specifico e risultano un semplice aggregato di attributi, è stato risolto grazie all'intervento del #cardin, che nel meeting ha spiegato al gruppo il significato di questo tipo di classi, chiamate _anemiche_, e ha asserito che la loro implementazione è sensata, poiché il raggruppamento di dati correlati in una classe aiuta ad avere una struttura più pulita ed un'organizzazione più flessibile.
=== Business Logic
Il gruppo ha discusso sull'effettiva presenza della business logic in seguito al feedback ricevuto dal #cardin. Questa è stata individuata principalmente nella parte che interroga l’API REST esterna e negli oggetti che rappresentano le istanze del database.\
Si è discusso il modo in cui gli oggetti della business logic devono essere convertiti in oggetti della presentation logic, e si è posta la norma di non utilizzare gli oggetti ritornati dalle API direttamente nella webapp.\
In seguito alle osservazioni del #cardin, si è deciso di implementare due diverse applicazioni, una per il backend e una per il frontend, entrambe con architettura a strati.
=== Design Pattern
Il gruppo, su consiglio del #cardin, decide di inserire design pattern solo se ritenuti necessari, anche perché la loro implementazione porta ad overhead. I pattern ad ora individuati sono:
+ middleware: per separare frontend da backend;
+ provider: tipico in React per passare variabili tra Componenti per evitare Prop Drilling.
=== Valutazione #adr
Il gruppo decide di proseguire con l'approfondimento dell'#adr, e si fissa come data massima di consegna per la rivalutazione la PB.
== Pianificazione
#let table-json(data) = {
let keys = data.at(0).keys()
table(
align: left,
columns: keys.len(),
..keys,
..data.map(
row => keys.map(
key => row.at(key, default: [n/a])
)
).flatten()
)
}
#figure(caption: [Task pianificate in seguito al colloquio con il #cardin.],
table-json(json("tasks.json"))
)
|
|
https://github.com/max-niederman/CS250 | https://raw.githubusercontent.com/max-niederman/CS250/main/hw/7.typ | typst | #import "../lib.typ": *
#show: homework.with(title: "CS 250 Homework #7")
= Probability
== 1
1. There are three independent coinflips, each with two possible outcomes; therefore there are $2^3 = 8$ outcomes in the sample space.
2. The event that there is 1 head and 2 tails is ${"HTT", "THT", "TTH"}$ with cardinality 3. Each outcome is equiprobable, so the probability of this event is $3/8$.
3. The event that every coin comes up tails is ${"TTT"}$ with cardinality 1. Each outcome is equiprobable, so the probability of this event is $1/8$.
4. "No coins come up heads" is logically equivalent to "every coin comes up tails", so the probability of this event is also $1/8$.
5. There is no intersection between getting all heads and getting all tails, so the probability of getting either is the sum of their probabilities, $1/8 + 1/8 = 1/4$. (The probability of HHH is also $1/8$ by symmetry because the coin is fair.)
6. As mentioned in the previous question, there is no intersection between the events, so the probability of their intersection is zero.
== 2
7. There are two independent rolls, each with six possible outcomes; therefore there are $6^2 = 36$ outcomes in the sample space.
8. The event of "snake eyes" is ${"11"}$ with cardinality one. Each outcome is equiprobable, so the probability of this event is $1/36$.
9. The event of "doubles" is ${"11", "22", "33", "44", "55", "66"}$ with cardinality six. Each outcome is equiprobable, so the probability of this event is $6/36 = 1/6$.
10. The probability of getting one on neither roll is $(5/36)^2$, so the probability of getting one on at least one roll is its complement, $1 - (5/36)^2$.
11. The event of "sum of 7" is ${"16", "25", "34", "43", "52", "61"}$ with cardinality six. Each outcome is equiprobable, so the probability of this event is $6/36 = 1/6$.
12. The event of getting two consecutive numbers is ${"12", "23", "34", "45", "56"}$ with cardinality five. Each outcome is equiprobable, so the probability of this event is $5/36$.
13. The event of getting a total greater than 10 is ${"55", "56", "65", "66"}$ with cardinality four. Each outcome is equiprobable, so the probability of this event is $4/36 = 1/9$.
14. Getting an odd total is logically equivalent to getting dice with different parities, which is the negation of getting dice with the same parity. The probability of getting dice with the same parity is $1/2$, so the probability of getting dice with different parities is $1 - 1/2 = 1/2$.
== 3
#[
#set enum(numbering: "a.")
+ $P(not E_2) = 1 - P(E_2) = 1 - 0.45 = 0.55$
+ $P(E_1 union E_2) = P(E_1) + P(E_2) - P(E_1 sect E_2) = 0.37 + 0.45 - 0.14 = 0.68$.
+ This event is the complement of $E_1 union E_2$, so its probability is $1 - 0.68 = 0.32$.
]
== 4
#[
#set enum(numbering: "a.")
+ By the addition principle, $P(E_1) = P(1) + P(3) + P(5) = 0.2 + 0.1 + 0.3 = 0.6$.
+ By the addition principle, $P(E_2) = P(3) + P(6) = 0.1 + 0.15 = 0.25$.
+ $E_3 = {4, 5, 6}$, so by the addition principle, $P(E_3) = P(4) + P(5) + P(6) = 0.2 + 0.3 + 0.15 = 0.65$.
+ $E_2 sect E_3$ contains only the outcome 6, so $P(E_2 sect E_3) = P(6) = 0.15$.
+ $E_1 union E_3$ consists of outcomes 1, 3, 4, 5, and 6, so by the addition principle, $P(E_1 union E_3) = P(1) + P(3) + P(4) + P(5) + P(6) = 0.2 + 0.1 + 0.2 + 0.3 + 0.15 = 0.95$.
]
== 5
Let $S$ be the event that the student plays one or more sports and $G$ be the event that the student graduates.
We are given that $P(S) = 0.72$ and $P(S sect G) = 0.67$,
and asked to find $P(G | S)$.
By the definition of conditional probability, $P(G | S) = P(S sect G) / P(S)$, so
$ P(G | S) = 0.67/0.72 approx #calc.round(digits: 2, 0.67/0.72)$.
= Relations
== 1
#[
#set enum(numbering: "a.")
+ Many-to-many
+ Many-to-one
+ One-to-one
+ One-to-many
]
== 2
#let rrho = $class("relation", rho)$
#let rsigma = $class("relation", sigma)$
#[
#set enum(numbering: "a.")
+ $rho union sigma$ is satisfied by $(2, 6)$ and $(3, 17)$, but not by $(2, 1)$. It is satisfied by $(0, 0)$ iff $0 divides 0$, which depends on the exact definition of divisibility being used.
+ $rho sect sigma$ is satisfied by $(2, 12)$ because $2 rrho 12 and 2 rsigma 12$, but not by $(3, 6)$ or $(1, 2)$ because neither satisfy $sigma$.
+ None of the pairs satisfy $rho'$, b ecause in each case the first element divides the second.
+ The relation $sigma'$ is satisfied by $(1, 1)$ and $(4, 8)$ but not by $(2, 10)$ because $5(2) <= 10$.
]
== 3
#[
#set enum(numbering: "a.")
+ $rho sect sigma$ is the relation "lives and works in".
+ $rho union sigma$ is the relation "lives and/or works in".
+ $rho sect sigma'$ is the relation "lives but doesn't work in".
+ $rho' union sigma$ is the relation "works but doesn't live in".
]
== 4
#[
#set enum(numbering: "a.")
+ $rho$ is reflexive, neither symmetric nor antisymmetric, and not transitive.
+ $rho$ is reflexive, symmetric, antisymmetric, and transitive.
+ $rho$ is not transitive, symmetric, antisymmetric, or reflexive.
+ $rho$ is transitive and antisymmetric but not symmetric or reflexive.
]
== 5
#[
#set enum(numbering: "a.")
+ $rho$ is reflexive and antisymmetric, but not symmetric or transitive.
+ $rho$ is symmetric and transitive, but not reflexive or antisymmetric.
+ $rho$ is symmetric and transitive, but not reflexive or antisymmetric.
+ $rho$ is reflexive, symmetric, and transitive, but not antisymmetric.
+ $rho$ is symmetric, transitive, and antisymmetric, but not reflexive.
]
== 6
#[
#set enum(numbering: "a.")
+ Yes to both.
By definition, $rho, sigma supset.eq { (s, s) | s in S }$, so their union and intersection are also supersets of this set, and therefore reflexive.
+ Yes to both.
In the case of $rho union sigma$, if we choose $(a, b) in rho union sigma$, then either $(a, b) in rho$ or $(a, b) in sigma$. In either case, because $rho$ and $sigma$ are symmetric, $(b, a) in rho$ or $(b, a) in sigma$, so $(b, a) in rho union sigma$.
For $rho sect sigma$, if we choose $(a, b) in rho sect sigma$, then $(a, b) in rho$ and $(a, b) in sigma$. Because $rho$ and $sigma$ are symmetric, $(b, a) in rho$ and $(b, a) in sigma$, so $(b, a) in rho sect sigma$.
+ $rho sect sigma$ is antisymmetric, but $rho union sigma$ is not necessarily.
For $rho sect sigma$, if we take $a, b in S$ such that $(a, b), (b, a) in rho sect sigma$, then $(a, b), (b, a) in rho$. Because $rho$ is antisymmetric, $a = b$.
A counterexample for $rho union sigma$ is $S = {1, 2}$, $rho = {(1, 2)}$, and $sigma = {(2, 1)}$. Then $(1, 2), (2, 1) in rho union sigma$, but $1 != 2$.
+ $rho sect sigma$ is transitive, but $rho union sigma$ is not necessarily.
For $rho sect sigma$, if we take $a, b, c in S$ such that $(a, b), (b, c) in rho sect sigma$, then $(a, b), (b, c) in rho$ and $(a, b), (b, c) in sigma$. Because $rho$ and $sigma$ are transitive, $(a, c) in rho$ and $(a, c) in sigma$, so $(a, c) in rho sect sigma$.
A counterexample for $rho union sigma$ is $S = {1, 2}$, $rho = {(1, 2)}$, and $sigma = {(2, 1)}$. Then $(1, 2), (2, 1) in rho union sigma$, but $(1, 1) in.not rho union sigma$.
]
== 7
#[
#set enum(numbering: "a.")
+ $rho$ is its own reflexive closure. Its symmetric closure is $rho union {(3, 2), (2, 1)}$ and its transitive closure is $rho union {(3, 2), (2, 1)}$.
+ $rho$ is its own reflexive, symmetric, and transitive closure.
+ The reflexive closure of $rho$ is $rho union {(2, 2), (3, 3)}$, its symmetric closure is $rho union {(2, 1), (3, 2)}$, and its transitive closure is $rho union {(2, 1), (3, 2)}$.
+ $rho$ is its own transitive closure. Its reflexive closure is $rho union {(2, 2), (3, 3)}$ and its symmetric closure is $rho union {(2, 1), (3, 2), (3, 1)}$.
]
== 8
#[
#set enum(numbering: "a.")
+ $rho$ is its own reflexive closure. Its symmetric closure is $rho union {(1, 0), (2, 1), (4, 2), (6, 4)}$ and its transitive closure is $rho union {(0, 2), (1, 4), (2, 6), (0, 4), (0, 6), (1, 6)}$.
+ The reflexive closure of $rho$ is $rho union {(0, 0), (1, 1), (2, 2), (4, 4), (6, 6)}$, its symmetric closure is itself, and its transitive closure is $rho union {(0, 0), (1, 1), (2, 2), (4, 4), (6, 6), (2, 6), (6, 2)}$.
+ The reflexive closure of $rho$ is $rho union {(4, 4), (6, 6)}$, and it is its own symmetric and transitive closure.
+ $rho$ is its own reflexive, symmetric, and transitive closure.
+ $rho$ is its own symmetric and transitive closure. Its reflexive closure is ${(0, 0), (1, 1), (2, 2), (4, 4), (6, 6)}$.
]
= Functions
== 1
#[
#set enum(numbering: "a.")
+ $f(S) = {3, 7}$
+ $f(S) = {1, 3}$
+ $f(S) = {2, 1, 0}$
]
== 2
#[
#set enum(numbering: "a.")
+ False. All function bring all elements of their domain to an image, but not all functions are surjective.
+ False. Take the function $f : NN -> NN = n |-> 1$. Every element in the codomain, $NN$, has an image under $f$, but $f$ is not surjective because $NN != {1}$.
+ True. If every element in the codomain has a preimage under $f$, then by unioning the images of all the preimages, we get that the range is superset of the codomain. The range is a subset of the codomain by definition, so the range is equal to the codomain and $f$ is surjective by definition.
+ True. Assume that such a function $f$ does exist. By the pigeonhole principle, at least one element in $f$'s codomain has more than one preimage, violating the assumption that $f$ is injective.
]
== 3
#[
#set enum(numbering: "a.")
+ Not a function from $S$ to $T$.
+ A function from $S$ to $T$. Neither one-to-one nor onto.
+ A function from $S$ to $T$. One-to-one and onto.
+ Not a function from $S$ to $T$.
+ Not a function from $S$ to $T$.
]
== 4
#[
#set enum(numbering: "a.")
+ This is not a function because some U.S. citizens either do not have middle initials or have middle initials beginning with characters not in any alphabet (e.g. ideograms or syllabograms).
+ This is a function because every person has exactly one birthday. It is onto but not one-to-one because people have been born on every day and multiple people can the same birthday.
+ This is not a function because not all U.S. citizens have social security numbers.
] |
|
https://github.com/MALossov/YunMo_Doc | https://raw.githubusercontent.com/MALossov/YunMo_Doc/main/template/font.typ | typst | Apache License 2.0 | // 字体定义
#let heiti = ("Times New Roman", "Noto Sans CJK SC")
#let songti = ("Times New Roman", "Noto Serif CJK SC")
#let kaiti = ("Times New Roman", "HYKaiTi")
#let fangsong = ("Times New Roman", "HYFangSong")
// 字号设置
// -----------------
// 2023/4/11 update log：
// - 增加了对于字号的设置，便于后续修改
#let font_size = (
yihao: 26pt,
xiaoyi: 24pt,
erhao: 22pt,
xiaoer: 18pt,
sanhao: 16pt,
xiaosan: 15pt,
sihao: 14pt,
xiaosi: 12pt,
wuhao: 10.5pt,
xiaowu: 9pt,
) |
https://github.com/nicolasfara/Template-for-Typst-Slides | https://raw.githubusercontent.com/nicolasfara/Template-for-Typst-Slides/master/Template-for-Typst-Slides.typ | typst | Apache License 2.0 | #import "@preview/touying:0.5.2": *
#import themes.metropolis: *
#import "@preview/fontawesome:0.1.0": *
#import "@preview/ctheorems:1.1.2": *
#import "@preview/numbly:0.1.0": numbly
// Pdfpc configuration
// typst query --root . ./example.typ --field value --one "<pdfpc-file>" > ./example.pdfpc
#let pdfpc-config = pdfpc.config(
duration-minutes: 30,
start-time: datetime(hour: 14, minute: 10, second: 0),
end-time: datetime(hour: 14, minute: 40, second: 0),
last-minutes: 5,
note-font-size: 12,
disable-markdown: false,
default-transition: (
type: "push",
duration-seconds: 2,
angle: ltr,
alignment: "vertical",
direction: "inward",
),
)
// Theorems configuration by ctheorems
#show: thmrules.with(qed-symbol: $square$)
#let theorem = thmbox("theorem", "Theorem", fill: rgb("#eeffee"))
#let corollary = thmplain(
"corollary",
"Corollary",
base: "theorem",
titlefmt: strong
)
#let definition = thmbox("definition", "Definition", inset: (x: 1.2em, top: 1em))
#let example = thmplain("example", "Example").with(numbering: none)
#let proof = thmproof("proof", "Proof")
#show: metropolis-theme.with(
aspect-ratio: "16-9",
footer: self => self.info.institution,
config-common(
// handout: true,
preamble: pdfpc-config,
),
config-info(
title: [Title],
subtitle: [Subtitle],
author: [Authors],
date: datetime.today(),
institution: [Institution],
// logo: emoji.school,
),
)
#set text(font: "Fira Sans", weight: "light", size: 20pt)
#show math.equation: set text(font: "Fira Math")
// #set heading(numbering: numbly("{1}.", default: "1.1"))
#title-slide()
// == Outline <touying:hidden>
// #components.adaptive-columns(outline(title: none, indent: 1em))
= Animation
== Simple Animation
#pdfpc.speaker-note("This is a note that only the speaker will see.")
// #set text(font: "Fira Sans", weight: 350, size: 20pt)
// #show math.equation: set text(font: "Fira Math")
// #set strong(delta: 200)
// #set par(justify: true)
// #set quote(block: true)
// #show quote: set align(left)
// #show quote: set pad(x: 2em, y: -0.8em)
// #set raw(tab-size: 4)
// #show raw.where(block: true): block.with(
// fill: luma(240),
// inset: 1em,
// radius: 0.7em,
// width: 100%,
// )
// #show bibliography: set text(size: 0.8em)
// #show footnote.entry: it => {
// block(inset: (x: 2em, y: 0.1em))[#text(size: 0.75em)[#it.note.body]]
// }
// #let fcite(clabel) = {
// footnote(cite(form: "full", label(clabel)))
// }
// #let author = block(inset: 0.1em)[
// #table(inset: 0.5em, stroke: none, columns: (auto, 4fr), align: (left, left),
// [#alert[*Author 1*]], [`<EMAIL>`],
// [Author 2], [`<EMAIL>`],
// [Author 3], [`<EMAIL>`],
// )
// #place(right, dy:-1.5em)[
// #figure(image("images/disi.svg", width:40%))
// ]
// ]
// #title-slide(
// title: "Slide Title",
// subtitle: "Subtitle",
// author: author,
// // date: datetime.today().display("[day] [month repr:long] [year]"),
// )
// #new-section-slide("Slide section 1")
// #slide(title: "Slide")[
// *Bold* and _italic_ text.
// This is a citiation @nicolas_farabegoli_2024_10535841.
// #alert[
// This is an alert.
// ]
// ]
// #slide(title: "Code slide")[
// ```kotlin
// fun main() {
// println("Hello, world!")
// for (i in 0..9) {
// println(i)
// }
// println("Goodbye, world!")
// }
// ```
// ]
// #slide[
// = This is a title
// #lorem(24)
// == This is a subtitle
// #lorem(34)
// ]
// #slide[
// == Icon in a title #fa-java()
// #fa-icon("github", fa-set: "Brands") -- Github icon
// #fa-icon("github", fa-set: "Brands", fill: blue) -- Github icon blue fill
// ]
// #slide[
// #bibliography("bibliography.bib")
// ]
|
https://github.com/francescoo22/LCD-exercises | https://raw.githubusercontent.com/francescoo22/LCD-exercises/main/src/rules.typ | typst | #import "common.typ": *
#let r = prooftree(
axiom($$),
axiom($$),
rule(n:2, label: "", $$),
)
// ****************** CCS_seq RULES ******************
#let r1 = prooftree(
axiom(""),
rule(label: "End-Zero", $0 ended$),
)
#let r2 = prooftree(
axiom($P ended$),
axiom($Q ended$),
rule(n:2, label: "End-Par", $P|Q ended$),
)
#let r3 = prooftree(
axiom($P ended$),
rule(label: "End-Hide", $P without A ended$),
)
#let r4 = prooftree(
axiom($P ended$),
rule(label: "End-Red", $P[f] ended$),
)
#let r5 = prooftree(
axiom($P ended$),
rule(label: (left: "End-Const", right: $space fi K def P$), $K ended$),
)
#let r6 = prooftree(
axiom($P ended$),
axiom($Q ended$),
rule(n:2, label: "End-Seq", $P ; Q ended$),
)
#let r7 = prooftree(
axiom($P atrans P'$),
rule(label: "Seq-L", $P;Q atrans P';Q$),
)
#let r8 = prooftree(
axiom($P ended$),
axiom($Q atrans Q'$),
rule(n:2, label: "Seq-R", $P;Q atrans Q'$),
)
// ****************** CLASSIC RULES ******************
#let c1 = prooftree(
axiom($$),
rule(label: "Act", $alpha . P atrans P$),
)
#let c2 = prooftree(
axiom($P_j atrans P_j '$),
rule(label: (left: "Sum", right: $space j in J$), $sum_(j in J) P_j atrans P_j '$),
)
#let c3 = prooftree(
axiom($P atrans P'$),
rule(label: "Par-1", $P|Q atrans P'|Q$),
)
#let c4 = prooftree(
axiom($Q atrans Q'$),
rule(label: "Par-2", $P|Q atrans P|Q'$),
)
#let c5 = prooftree(
axiom($P atrans P'$),
axiom($Q ->^overline(alpha) Q'$),
rule(n:2, label: "Par-3", $P|Q ->^tau P'|Q'$),
)
#let c6 = prooftree(
axiom($P atrans P'$),
rule(label: (left: "Hide", right: $space alpha, overline(alpha) in.not L$), $P without L atrans P' without L$),
)
#let c7 = prooftree(
axiom($P atrans P'$),
rule(label: "Red", $P[f] ->^f(a) P'[f]$),
)
#let c8 = prooftree(
axiom($P atrans P'$),
rule(label: (left: "Const", right: $space K def P$), $K atrans P'$),
)
// ****************** RULES FOR THE PROOF ******************
#let p1 = prooftree(
axiom($$),
rule(label: "Act", $alpha . e(P) atrans e(P)$),
rule(label: (left: "Hide", right: $alpha != nu "by construction"$), $e(alpha . P) wnu = alpha . e(P) wnu atrans e(P) wnu$),
)
#let p2 = prooftree(
axiom($e(P) atrans P''$),
rule(label: (left: "Const", right: $K_e def e(P)$), $K_e atrans P''$),
rule(label: (left: "Hide", right: $alpha != nu "by construction"$), $e(K) wnu = K_e wnu atrans P'' wnu$),
)
#let p3 = prooftree(
axiom($e(P) awtrans P''$),
rule(label: (left: "Hide", right: $alpha, overline(alpha) in.not L$), $e(P wL) = e(P) wL awtrans P'' wL$),
rule(label: (left: "Hide", right: $alpha, overline(alpha) in.not {nu}$), $e(P wL) wnu awtrans P'' wL wnu$),
)
#let p4 = prooftree(
axiom($e(P) awtrans P''$),
rule(label: "Red", $e(P) [f] =>^(f(alpha)) P'' [f]$),
rule(label: "Hide", $e(P[f]) wnu = e(P) [f] wnu =>^(f(alpha)) P'' [f] wnu$),
)
#let p5 = prooftree(
axiom(label: "Act", $alpha_j . P_j ->^(alpha_j) P_j$),
rule(label: (left: "Sum", right: $space j in J$), $sum_(j in J != emptyset) alpha_j . P_j ->^(alpha_j) P_j$),
)
#let p6 = prooftree(
axiom(label: "Act", $alpha_j . e(P_j) ->^(alpha_j) e(P_j)$),
rule(label: (left: "Sum", right: $space j in J$), $sum_(j in J != emptyset) alpha_j . e(P_j) ->^(alpha_j) e(P_j)$),
rule(label: (left: "Hide", right: $alpha_j != nu$), $e(sum_(j in J != emptyset) alpha_j . P_j) wnu = sum_(j in J != emptyset) alpha_j . e(P_j) wnu ->^(alpha_j) e(P_j) wnu$),
)
#let p7 = prooftree(
axiom($e(P) atrans P''$),
rule(label: (left: "Red", right: $alpha != nu => [nu'/nu] (alpha) = alpha$), $e(P)[nu'/nu] atrans P''[nu'/nu]$),
rule("..."),
rule(label: "", $e(P | Q) wnu = (e(P)[nu'/nu] | e(Q)[nu'/nu] | overline(nu') . overline(nu') . nu . 0) wnup wnu atrans (P''[nu'/nu] | e(Q)[nu'/nu] | overline(nu') . overline(nu') . nu . 0) wnup wnu$)
)
#let p8 = prooftree(
axiom($e(P) atrans P''$),
rule(label: "Red", $e(P)[nu'/nu] ->^([nu'/nu](alpha) = alpha) P''[nu'/nu]$),
rule("..."),
rule($e(P;Q) wnu = (e(P)[nu'/nu] | overline(v') . e(Q)) wnup wnu atrans (P''[nu'/nu] | overline(v') . e(Q)) wnup wnu$),
)
#let p9 = prooftree(
axiom($e(P) ->^(tau*) P_"temp"$),
rule(label: "Red", $e(P)[nu'/nu] ->^([nu'/nu](tau*) = tau*) P_"temp" [nu'/nu]$),
rule("..."),
rule($(e(P) [nu'/nu] | overline(nu') . e(Q)) wnup wnu ->^(tau*) (P_"temp" [nu'/nu] | overline(nu') . e(Q)) wnup wnu$),
)
#let p10 = prooftree(
axiom($P_"temp" ntrans P'$),
rule(label: "Red", $P_"temp" [nu'/nu] ->^([nu'/nu](nu) = nu') P' [nu'/nu]$),
axiom($overline(nu') . e(Q) ->^(overline(nu')) e(Q)$),
rule(n:2, "..."),
rule($(P_"temp" [nu'/nu] | overline(nu') . e(Q)) wnup wnu ->^(tau) (P' [nu'/nu] | e(Q)) wnup wnu$),
)
#let p11 = prooftree(
axiom($e(Q) atrans Q''$),
rule("..."),
rule($(P' [nu'/nu] | e(Q)) wnup wnu atrans (P' [nu'/nu] | Q'') wnup wnu$),
)
#let r = prooftree(
axiom($$),
axiom($$),
rule(n:2, label: "", $$),
)
|
|
https://github.com/typst-doc-cn/tutorial | https://raw.githubusercontent.com/typst-doc-cn/tutorial/main/src/mod.typ | typst | Apache License 2.0 | #import "/src/book.typ"
#import "/typ/templates/page.typ"
#import "/typ/templates/term.typ": _term
#import "/typ/templates/side-notes.typ": side-note, side-attrs
#import "/typ/templates/page.typ": main-color
#import "/typ/typst-meta/docs.typ": typst-v11
#let refs = {
let cl = book.cross-link
(
writing-markup: cl.with("/basic/writing-markup.typ"),
writing-scripting: cl.with("/basic/writing-scripting.typ"),
scripting-base: cl.with("/basic/scripting-base.typ"),
scripting-complex: cl.with("/basic/scripting-complex.typ"),
scripting-modules: cl.with("/intermediate/scripting-modules.typ"),
content-scope-style: cl.with("/intermediate/content-scope-and-style.typ"),
content-stateful: cl.with("/intermediate/content-stateful.typ"),
ref-typebase: cl.with("/basic/reference-typebase.typ"),
ref-type-builtin: cl.with("/basic/reference-type-builtin.typ"),
ref-color: cl.with("/basic/reference-color.typ"),
ref-visualization: cl.with("/basic/reference-visualization.typ"),
ref-bibliography: cl.with("/basic/reference-bibliography.typ"),
ref-datetime: cl.with("/basic/reference-date.typ"),
ref-math-mode: cl.with("/basic/reference-math-mode.typ"),
ref-math-symbols: cl.with("/basic/reference-math-symbols.typ"),
ref-data-process: cl.with("/basic/reference-data-process.typ"),
ref-wasm-plugin: cl.with("/basic/reference-wasm-plugin.typ"),
ref-grammar: cl.with("/basic/reference-grammar.typ"),
ref-layout: cl.with("/intermediate/reference-layout.typ"),
ref-length: cl.with("/intermediate/reference-length.typ"),
misc-font-setting: cl.with("/misc/font-setting.typ"),
)
}
#let term-list = (
"array literal": "数组字面量",
"blocky raw block": "块代码片段",
"boolean literal": "布尔字面量",
"code mode": "脚本模式",
"codepoint": "码位",
"codepoint width": "码位宽度",
"character": "字符",
"comment": "注释",
"content": "内容",
"consistency": "一致性",
"content block": "内容块",
"delimiter": "定界符",
"dictionary literal": "字典字面量",
"floating-point literal": "浮点数字面量",
"function identifier": "函数名标识符",
"emphasis semantics": "强调语义",
"escape sequences": "转义序列",
"exponential notation": "指数表示法",
"expression": "表达式",
"field": "域成员",
"field access": "访问域成员",
"function body expression": "函数体表达式",
// https://developer.mozilla.org/zh-CN/docs/Web/JavaScript/Reference/Global_Objects/String
"grapheme cluster": "字素簇",
"grapheme cluster width": "字素簇宽度",
"initialization expression": "初始值表达式",
"integer literal": "整数字面量",
"interpret": "解释",
"interpreter": "解释器",
"interpreting mode": "解释模式",
"introspection function": "自省函数",
"lexicographical order": "字典序",
"line break": "换行符",
"literal": "字面量",
"markup mode": "标记模式",
"math mode": "数学模式",
"none literal": "空字面量",
"nearest": "最近",
"raw block": "代码片段",
"representation": "表示法",
"parameter identifier": "参数标识符",
"parser": "解析器",
"pattern": "模式串",
"placeholder": "占位符",
"shorthand": "速记符号",
"scripting": "脚本",
"string literal": "字符串字面量",
"strong semantics": "着重语义",
"syntactic predecessor": "语法前驱",
"tilde diacritical marks": "波浪变音符号",
"type": "类型",
"utf-8 encoding": "UTF-8编码",
"value": "值",
"variable identifier": "变量名标识符",
"whitespace": "空白字符",
)
#let mark-list = (
"=": "等于号",
"*": "星号",
"#": "井号",
"_": "下划线",
"`": "反引号",
"hyphen": "连字号",
"-": "减号",
"+": "加号",
"\\": "反斜杠",
"/": "斜杠",
"~": "波浪号",
".": "点号",
";": "分号",
)
#let exec-code(cc, res: none, scope: (:), eval: eval) = {
rect(
width: 100%,
inset: 10pt,
{
// Don't corrupt normal headings
set heading(outlined: false)
if res != none {
res
} else {
eval(cc.text, mode: "markup", scope: scope)
}
},
)
}
// al: alignment
#let code(cc, code-as: none, res: none, scope: (:), eval: eval, exec-code: exec-code, al: left) = {
let code-as = if code-as == none {
cc
} else {
code-as
}
let vv = exec-code(cc, res: res, scope: scope, eval: eval)
if al == left {
layout(lw => style(styles => {
let width = lw.width * 0.5 - 0.5em
let u = box(width: width, code-as)
let v = box(width: width, vv)
let u-box = measure(u, styles)
let v-box = measure(v, styles)
let height = calc.max(u-box.height, v-box.height)
stack(
dir: ltr,
{
set rect(height: height)
u
},
1em,
{
rect(height: height, width: width, inset: 10pt, vv.body)
},
)
}))
} else {
code-as
vv
}
}
#let fg-blue = main-color.mix(rgb("#0074d9"))
#let pro-tip(content) = locate(loc => {
let attr = side-attrs.at(loc)
let ext = attr.width + attr.gutter
move(
dx: -ext,
block(
width: 100% + ext,
breakable: false,
inset: (x: 0.65em, y: 0.65em, left: 0.65em * 0.6),
radius: 4pt,
fill: rgb("#0074d920"),
{
set text(fill: fg-blue)
stack(
dir: ltr,
move(dy: 0.1em, image("/assets/files/info-icon.svg", width: 1em)),
0.2em,
box(width: 100% - 1.2em, v(0.2em) + content),
)
},
),
)
})
#let fg-red = main-color.mix(red)
#let todo-color = fg-red
#let todo-box(content) = locate(loc => {
let attr = side-attrs.at(loc)
let ext = attr.width + attr.gutter
move(
dx: -ext,
block(
width: 100% + ext,
breakable: false,
inset: (x: 0.65em, y: 0.65em, left: 0.65em * 0.6),
radius: 4pt,
fill: fg-red.transparentize(80%),
{
set text(fill: fg-red)
stack(
dir: ltr,
move(dy: 0.4em, text(size: 0.5em)[todo]),
0.2em,
box(width: 100% - 1.2em, v(0.2em) + content),
)
},
),
)
})
/// This function is to render a text string in monospace style and function
/// color in your defining themes.
///
/// ## Examples
///
/// ```typc
/// typst-func("list.item")
/// ```
///
/// Note: it doesn't check whether input is a valid function identifier or path.
#let typst-func(it) = [
#raw(it + "()", lang: "typc") <typst-raw-func>
]
#let show-answer = false
// #let show-answer = true
#let exercise(question, answer) = {
enum.item(question + if show-answer {
parbreak() + [答：] + answer
})
}
#let term(term, postfix: none, en: none) = _term(term-list, term, en: en, postfix: postfix)
#let mark(mark, postfix: none) = _term(
mark-list,
mark,
en: if mark == "hyphen" {
raw("-")
} else {
raw(mark)
},
postfix: postfix,
)
#let ref-bookmark = side-note
#let highlighter(it, k) = {
if k == "method" {
set text(fill: rgb("4b69c6"))
raw(it)
} else if k == "keyword" {
set text(fill: rgb("8b41b1"))
raw(it)
} else if k == "var" {
set text(fill: blue.mix(main-color))
raw(it)
} else {
raw(it)
}
}
#let darkify(clr) = clr.mix(main-color.negate()).saturate(30%)
#let ref-ty-locs = (
"int": refs.ref-typebase,
"bool": refs.ref-typebase,
"float": refs.ref-typebase,
"str": refs.ref-typebase,
"array": refs.ref-typebase,
"dict": refs.ref-typebase,
"none": refs.ref-typebase,
"ratio": refs.ref-length,
"alignment": refs.ref-layout,
"version": refs.ref-type-builtin,
"any": refs.ref-type-builtin,
"bytes": refs.ref-type-builtin,
"label": refs.ref-type-builtin,
"type": refs.ref-type-builtin,
"regex": refs.ref-type-builtin,
)
#let show-type(ty) = {
h(3pt)
ref-ty-locs.at(ty)(
reference: label("reference-type-" + ty),
box(fill: darkify(rgb("eff0f3")), outset: 2pt, radius: 2pt, raw(ty)),
)
h(3pt)
}
#let ref-signature(name, kind: "scope") = {
let fn = if kind == "scope" {
typst-v11.scoped-items.at(name)
} else if kind == "cons" {
let ty = typst-v11.types.at(name)
ty.body.content.constructor
} else {
typst-v11.funcs.at(name)
}
locate(loc => {
let attr = side-attrs.at(loc)
let ext = attr.width + attr.gutter
move(
dx: -ext,
block(
fill: rgb("#add5a220"),
radius: 2pt,
width: 100% + ext,
inset: (x: 1pt, y: 5pt),
{
set par(justify: false)
set text(fill: main-color.mix(rgb("eff0f3").negate()))
highlighter("fn", "keyword")
raw(" ")
highlighter(name, "method")
raw("(")
fn
.params
.map(param => {
highlighter(param.name, "var")
": "
param.types.map(show-type).join()
})
.join(raw(", "))
raw(")")
if fn.returns.len() > 0 {
raw(" ")
box(raw("->"))
raw(" ")
fn.returns.map(show-type).join()
}
},
),
)
})
}
#let ref-func-signature = ref-signature.with(kind: "func")
#let ref-cons-signature = ref-signature.with(kind: "cons")
#let ref-method-signature = ref-signature
|
https://github.com/Fwxzxh/MyResume | https://raw.githubusercontent.com/Fwxzxh/MyResume/main/README.md | markdown | # My Resume
This is my resume written in typst markup :D! |
|
https://github.com/Maso03/Bachelor | https://raw.githubusercontent.com/Maso03/Bachelor/main/Bachelorarbeit/chapters/GenAI.typ | typst | MIT License | == Generative Intelligenz (GenAI)
Generative Intelligenz (GenAI) bezeichnet eine Klasse von Künstlicher Intelligenz, die das Konzept von Maschinen umfasst, die menschliche Intelligenz imitieren. Dies geschieht mithilfe von maschinellem Lernen (ML), das Muster erkennt, und Deep Learning, das künstliche neuronale Netze verwendet. GenAI kann im Gegensatz zu "normalen" KI-Systemen neue Inhalte generieren, indem sie die Muster ihrer Trainingsdaten analysiert und versteht. Basierend auf diesen Technologien ist GenAI in der Lage, große Mengen an Daten zu verarbeiten und daraus relevante Inhalte zu erzeugen, wie Texte, Bilder, Musiknoten und mehr @IWWB @GoogleGenAI.
#figure(
image("/example/assets/GenAI.jpg", width: 50%),
caption: [Visualisierung von KI-Systemen, Quelle: Google Cloud],
) <cluster-single-node>
=== Modelle und Technologien
Es gibt verschiedene generative Modelle, die in der Forschung und Praxis eingesetzt werden. Im Detail werden die Transformers erklärt, über die anderen Modelle, welche weniger Bedeutung für diese Arbeit beinhalten, wird nur ein Überblick gegeben. @KI-Statista3 @RobotsAI @KI-Statista2:
==== *Generative Adversarial Networks (GANs):*
Diese bestehen aus einem Generator und einem Diskriminator, die gegeneinander arbeiten, um realistische Daten zu erzeugen.
Der Generator lernt Daten und generiert neue Beispiele, welche zu negativen Beispielen des Diskriminators werden.
Der Diskriminator lernt, zwischen echten und generierten Daten zu unterscheiden. Dabei bestraft der Diskriminator den Generator, wenn dieser schlechte Daten generiert.
Am Anfang sind die generierten Daten schlecht, aber mit der Zeit werden sie immer realistischer. Die Genauigkeit des Diskriminators steigt, bis er nicht mehr zwischen echten und generierten Daten unterscheiden kann @GAN @GoogleGAN.
#figure(
image("/example/assets/Graph1.png", width: 50%),
caption: [Generator und Diskriminator Verlust Kurve nach dem Training, Quelle: LernOpenCV],
) <cluster-single-node>
Das komplette System kann als Spiel zwischen zwei Spielern betrachtet werden, wobei der Generator versucht, den Diskriminator zu täuschen und der Diskriminator versucht, den Generator zu entlarven. Dieses Spiel führt zu einer Verbesserung der generierten Daten und kann für verschiedene Anwendungen wie Bildgenerierung, Textgenerierung und mehr verwendet werden.
Sowohl der Diskriminator als auch der Generator sind neuronale Netze, die miteinander interagieren und sich gegenseitig verbessern.
#figure(
image("/example/assets/ganSystem.svg", width: 60%),
caption: [Systemarchitektur, Quelle: Developers Google],
) <cluster-single-node>
Probleme enstehen, wenn der Diskriminator zu gut ist, dann versagt das System, da der Generator keine Chance hat, aufgrund des verschwindendes Gradients, gute Daten zu generieren.
GANs scheitern an der Konvergenz und sind schwer zu trainieren, da sie instabil sind. Es gibt verschiedene Ansätze, um diese Probleme zu lösen, wie zum Beispiel Wasserstein GANs oder das Hinzufügen von Rauschen um die Stabilität zu verbessern @GoogleGAN.
==== *Variational Autoencoders (VAEs):*
Diese Modelle lernen, die Daten in einem niedrigdimensionalen Raum zu repräsentieren und aus dieser Darstellung neue Daten zu generieren.
Autoencoder bestehen aus einer neuronalen Netzwerkarchitektur, welche für die Kompression und Rekonstruktion von Daten verwendet wird. Er besteht aus einem Encoder, der die Daten in einen niedrigdimensionalen Raum abbildet, und einem Decoder, der die Daten wieder in den ursprünglichen Raum zurückführt. Der Rekonstruktionsfehler sorgt für eine Übereinstimmung der Ausgabe mit der Eingabe. Das ist die Grundlage für das Verständnis von VAEs @VAEs.
Ein variationaler Autoencoder (VAE) bietet eine Möglichkeit, eine Beobachtung im latenten Raum zu beschreiben. Anstatt also einen Encoder zu bauen, der einen einzelnen Wert ausgibt, um jedes latente Zustandsattribut zu beschreiben, wird der Encoder so umformuliert, damit eine Wahrscheinlichkeitsverteilung für jedes latente Attribut entsteht. Das bedeutet, dass der Encoder eine Wahrscheinlichkeitsverteilung in der Engpassschicht angibt, anstatt nur einen einzelnen Ausgabewert @VAEs.
Der variante Autoencoder unterscheidet sich von einem Autoencoder in der Hinsicht, dass er eine statistische Weise zur Beschreibung der Stichproben des Datensatzes im latenten Raum bietet. Daher gibt der variationale Autoencoder eine Wahrscheinlichkeitsverteilung, in der Engpassschicht, anstelle eines einzelnen Ausgabewerts aus.
#figure(
image("/example/assets/VAEs.png", width: 60%),
caption: [Systemarchitektur des VAEs, Quelle: GeeksforGeeks],
) <cluster-single-node>
==== *Recurrent Neural Networks (RNNs):*
Recurrent Neural Networks (RNNs) unterscheiden sich von anderen neuronalen Netzwerken (NNs) durch ihre Fähigkeit, mit sequentiellen Daten zu arbeiten. Im Gegensatz zu herkömmlichen neuronalen Netzwerken, die typischerweise einen festen Inputwert haben und daraus eine Vorhersage ableiten, können RNNs mehrere Inputwerte in einer Sequenz verarbeiten.
Herkömmliche neuronale Netzwerke arbeiten in der Regel mit einer festen Anzahl an Eingabewerten, zum Beispiel mit einem einzigen Input oder mit einem 6x6-Pixel-Bild. Das bedeutet, der Input ist immer gleich und hat eine bestimmte, vorgegebene Anzahl an Werten. Wenn man jedoch Vorhersagen treffen möchte, die auf verschiedenen Inputsequenzen basieren, zum Beispiel auf den Werten 9 und 5, kommen RNNs ins Spiel.
RNNs verfügen, genau wie herkömmliche NNs, über Gewichtungen, Biases, Schichten und Aktivierungsfunktionen. Der wesentliche Unterschied besteht darin, dass RNNs Feedback-Loops besitzen. Diese Feedback-Loops ermöglichen es RNNs, sequentielle Eingaben zu verarbeiten, indem der aktuelle Input zusammen mit dem vorherigen Input berechnet wird, um eine Vorhersage zu treffen.
Bei der sequenziellen Eingabe wird jeder Input durch die Aktivierungsfunktion berechnet und dann der Output ausgegeben. Hier kommt die Feedback-Loop ins Spiel, die es erlaubt, den vorherigen Input in die Berechnung des aktuellen Inputs einzubeziehen. Dies macht RNNs besonders geeignet für Anwendungen, bei denen der Kontext vorheriger Eingaben entscheidend ist, wie zum Beispiel in der Textverarbeitung oder bei Zeitreihenanalysen.
Um die Flexibilität zu erhöhen, können RNNs durch das Erstellen mehrerer Input-Layer mit verschiedenen Eingaben und einer gleichen Anzahl an Outputs optimiert werden. Dabei wird der Output jeder Schicht an die nächste Schicht weitergegeben, wobei die Gewichtungen und Biases für alle Eingaben gleich bleiben. Egal, wie oft das RNN entfaltet wird, die Gewichtungen und Biases bleiben konstant für alle Daten, die trainiert werden @RNN.
#figure(
image("/example/assets/Rnn.svg", width: 60%),
caption: [Architektur des RNNs, Quelle: Analytics Vidhya],
) <cluster-single-node>
*Herausforderungen bei der Nutzung von RNNs*
RNNs werden in der Praxis oft weniger genutzt, weil sie mit zunehmender Entfaltungstiefe schwieriger zu trainieren sind. Ein wesentliches Problem ist das "Vanishing/Exploding Gradient Problem", das bei tiefen RNNs auftreten kann. Dieses Problem tritt auf, wenn die Gewichtungen in den Feedback-Loops entweder zu groß oder zu klein werden. Es gibt zwei Hauptprobleme, die durch das Vanishing/Exploding Gradient Problem entstehen können:
- *Explodierender Gradient:* Wenn RNNs zu oft entfaltet werden und die Gewichtungen größer als 1 sind, können bereits kleine Inputwerte zu extrem großen Zahlen führen. Beispielsweise kann ein Inputwert von 50 bei einer Gewichtung von 2 zu einem Output von $2^50$ führen, was eine zu große Zahl ist.
- *Verschwindender Gradient:* Wenn man sich auf Gewichtungen kleiner als 1 beschränkt, verschwindet der Gradient, der für die Berechnung der Backpropagation entscheidend ist. Zum Beispiel würde eine Gewichtung von 0,5 bei 50 Unroll-Schritten zu einem Wert von $0,5^50$ führen, was nahezu null ist und die Schritte somit zu klein macht.
Diese Probleme machen das Training von tiefen RNNs herausfordernd und sind ein Grund, warum sie in der Praxis oft durch andere Architekturen, wie Long Short-Term Memory (LSTM) Netzwerke oder Gated Recurrent Units (GRUs), ersetzt werden, die diese Probleme besser handhaben können @RNN.
==== *Transformers*
Transformers sind neuronale Netzwerke, die in der Lage sind, vielfältige Aufgaben zu bewältigen, wie zum Beispiel das Übersetzen von Texten, das Schreiben von Texten, das Generieren von Computercode oder Anwendungen in der Biologie, wie das Entfalten und Vorhersagen von Proteinen. Bekannte Modelle wie GPT, BERT und GEMINI basieren auf der Transformer-Architektur .
*Was sind Transformers?*
Transformers stellen einen speziellen Typ von neuronaler Netzwerkarchitektur dar. Während für die Verarbeitung von Bildern lange Zeit Convolutional Neural Networks (CNNs) verwendet wurden, und für sequentielle Daten wie Sprache Recurrent Neural Networks (RNNs) zum Einsatz kamen, bringen Transformers wesentliche Vorteile, insbesondere bei der Verarbeitung von Texten.
RNNs, wie bereits beschrieben, können sequenzielle Eingaben verarbeiten, was bedeutet, dass sie die Reihenfolge der Wörter berücksichtigen. Allerdings haben sie Schwierigkeiten, lange Texte zu verarbeiten und Kontext über große Textabschnitte hinweg zu behalten. Zudem ist das Training von RNNs aufgrund ihrer sequentiellen Natur sehr zeitaufwendig. Hier kommen Transformers ins Spiel, da sie parallel arbeiten können und dadurch große Modelle wie GPT-3 mit 45 Terabyte an Textdaten effizient trainiert werden können @AIAYN.
*Wie funktionieren Transformers?*
Transformers beruhen auf drei Hauptinnovationen: Positional Encoding, Attention und Self-Attention.
*Word Embedding*
Zunächst werden Wörter in numerische Werte konvertiert, indem ein einfaches neuronales Netzwerk jedem Wort ein einzigartiges Set von Zahlen zuweist. Diese numerischen Werte, oder Word Embeddings, ermöglichen es dem Modell, Wörter in einer für Maschinen verständlichen Form zu verarbeiten.
*Positional Encoding*
Beim Übersetzen eines Textes beispielsweise wird nicht sequenziell gearbeitet, sondern jedes Wort wird nummeriert und die Position im Satz wird durch eine Positionscodierung berücksichtigt. Dies geschieht mithilfe von sinus- und cosinus-Funktionen, um positionsspezifische Werte für jedes Word Embedding zu generieren.
*Self-Attention*
Eine der Herausforderungen beim Übersetzen von Texten ist, dass Sätze nicht einfach Wort für Wort übersetzt werden können, da verschiedene Sprachen unterschiedliche Satzstrukturen haben. Das Attention-Mechanismus betrachtet daher immer den gesamten Originalsatz und gibt Vorhersagen bzw. Wahrscheinlichkeiten an, welches Wort am ehesten an welcher Stelle im Zieltext stehen sollte. Dieses Verfahren wird durch eine große Menge an Daten unterstützt, aus denen das Modell lernt.
Die wahre Innovation der Transformers liegt in der Self-Attention. Während frühere Modelle nur die Anordnung der Wörter berücksichtigten, ermöglicht Self-Attention dem Modell, ein tieferes Verständnis der Sprache zu entwickeln. Das Modell lernt dabei automatisch Synonyme und sprachliche Regeln, indem es die Beziehungen zwischen den Wörtern im Kontext analysiert. Self-Attention berechnet für jedes Wort sogenannte Queries, Keys und Values, um Attention-Scores zu generieren, die helfen, die Beziehung zwischen den Wörtern zu etablieren.
*Residual Connections*
Residual Connections helfen beim Training komplexer neuronaler Netzwerke, indem sie sicherstellen, dass die Selbstaufmerksamkeitsschicht sich auf die Beziehungen zwischen den Eingabewörtern konzentrieren kann, ohne die Informationen zur Einbettung der Wörter und der Positionscodierung zu verlieren.
*Multi-head Attention*
Durch das Stapeln mehrerer Self-Attention-Schichten, die „Heads“ genannt werden, fängt der Transformer verschiedene Beziehungen zwischen den Wörtern ein. Das ursprüngliche Transformermodell verwendet acht solcher Heads.
*Encoding und Decoding*
Der Transformer besteht aus einem Encoder, der die Eingangssequenz verarbeitet, und einem Decoder, der die Ausgangssequenz erzeugt. Sowohl der Encoder als auch der Decoder verwenden Word Embedding, Positional Encoding, Self-Attention und Residual Connections. Der Decoder beginnt mit einem End-of-Sequence-Token (EOS) und generiert die Ausgabesequenz Schritt für Schritt.
*Normalization und Scaling*
Um große Vokabeln und lange Eingabe-/Ausgabesequenzen zu verarbeiten, normalisiert der Transformer die Werte nach jedem Schritt und skaliert die Produktwerte während der Aufmerksamkeitsberechnungen. Dies trägt zur Stabilität bei und verbessert die Leistung des Modells.
*Fully Connected Layers*
Nach der Verarbeitung mit Self-Attention und Residual Connections werden die Werte durch vollständig verbundene Schichten und eine Softmax-Funktion geleitet, um die endgültigen Ausgabe-Token zu generieren.
*Warum sind Transformers besser in der Praxis als RNNs?*
Transformers bieten mehrere Vorteile gegenüber RNNs:
- *Parallelisierung:* Im Gegensatz zu RNNs, die sequenziell arbeiten, können Transformers Eingaben parallel verarbeiten. Dies führt zu deutlich schnelleren Trainingszeiten und ermöglicht die Verarbeitung großer Datensätze.
- *Kontextbewusstsein:* Durch Self-Attention können Transformers den Kontext eines Wortes besser verstehen und über längere Textabschnitte hinweg beibehalten, was zu besseren Vorhersagen und Übersetzungen führt.
- *Effizienz:* Die parallele Verarbeitung und die Möglichkeit, große Modelle effizient zu trainieren, machen Transformers zu einer leistungsstarken Architektur für viele Anwendungen, die auf großen Datenmengen beruhen.
Diese Eigenschaften haben Transformers in vielen Bereichen zu einem bevorzugten Modell gemacht, sei es bei der maschinellen Übersetzung, der Textgenerierung oder anderen Anwendungen der natürlichen Sprachverarbeitung.
#figure(
image("/example/assets/Transformers.svg", width: 40%),
caption: [Architektur des Transformers, Quelle: Cornell University @AIAYN],
) <cluster-single-node>
== Spracherkennungstechnologien
Spracherkennungstechnologien ermöglichen es Computern, gesprochene Sprache zu erkennen und zu verarbeiten. Diese Technologien nutzen komplexe Algorithmen und maschinelles Lernen, um Sprachmuster zu analysieren und in Text umzuwandeln. Anwendungen finden sich in virtuellen Assistenten, Transkriptionsdiensten und interaktiven Sprachanwendungen. Fortschritte in der Spracherkennung haben die Genauigkeit und Benutzerfreundlichkeit dieser Systeme erheblich verbessert.
== Datenmanagement
Datenmanagement bezieht sich auf die Prozesse und Systeme, die verwendet werden, um Daten zu sammeln, zu speichern, zu organisieren und zu pflegen. Effektives Datenmanagement ist entscheidend für die Gewährleistung der Datenqualität, -sicherheit und -zugänglichkeit. In der Entwicklung von KI-Systemen spielen Daten eine zentrale Rolle, da sie die Grundlage für das Training und die Verbesserung von Modellen bilden. Ein robustes Datenmanagementsystem ermöglicht es, große Datenmengen effizient zu handhaben und die Integrität und Vertraulichkeit der Daten zu schützen.
== Marktanalyse
Die Marktanalyse umfasst die Untersuchung von Marktbedingungen, Wettbewerbslandschaften und Verbraucherverhalten, um fundierte Geschäftsentscheidungen zu treffen. Im Kontext von KI- und VR-Technologien hilft eine Marktanalyse, die Potenziale und Herausforderungen dieser Technologien zu verstehen. Sie liefert Einblicke in aktuelle Trends, Wachstumschancen und mögliche Marktbarrieren. Für die Entwicklung eines KI-basierten Chat-Avatars, der in verschiedenen Branchen eingesetzt werden kann, ist eine gründliche Marktanalyse unerlässlich, um die Bedürfnisse der Zielgruppe zu identifizieren und die Markteinführungsstrategie zu planen.
Diese Grundlagen bilden das Fundament für die Entwicklung eines interaktiven, KI-gestützten 3D-Avatars, der in der Lage ist, Nutzern kontextbezogene Unterstützung und Beratung zu bieten.
== Anforderungen an den 3D-Avatar |
https://github.com/typst/packages | https://raw.githubusercontent.com/typst/packages/main/packages/preview/jogs/0.1.0/README.md | markdown | Apache License 2.0 | # Jogs
Quickjs javascript runtime for typst. This package provides a typst plugin for evaluating javascript code.
## Example
````typst
#import "@preview/jogs:0.1.0": *
#set page(height: auto, width: auto, fill: black)
#set text(fill: white)
#show raw.where(lang: "jogs"): it => eval-js(it)
```jogs
let a = {a: 0, c: 1, b: "123"}
let res = []
function fib(n) {
if (n < 2) return n
return fib(n - 1) + fib(n - 2)
}
for (let i = 0; i < 10; i++) {
res.push(fib(i))
}
a.d = res
a
```
````
result:
## Documentation
This package provide following function(s):
### `eval-js`
Run a Javascript code snippet.
#### Arguments
* `code` - The Javascript code to run. It can be a string or a raw block.
#### Returns
The result of the Javascript code. The type is the typst type which most closely resembles the Javascript type.
#### Example
```typ
#let result = eval-js("1 + 1")
```
|
https://github.com/SeniorMars/tree-sitter-typst | https://raw.githubusercontent.com/SeniorMars/tree-sitter-typst/main/examples/layout/enum.typ | typst | MIT License | // Test enumerations.
---
#enum[Embrace][Extend][Extinguish]
---
1. First.
2. Indented
+ Second
---
// Test automatic numbering in summed content.
#for i in range(5) {
[+ #numbering("I", 1 + i)]
}
---
// Mix of different lists
- Bullet List
+ Numbered List
/ Term: List
---
// Edge cases.
+
Empty
+Nope
|
https://github.com/sses7757/sustech-graduated-thesis | https://raw.githubusercontent.com/sses7757/sustech-graduated-thesis/main/sustech-graduated-thesis/utils/degree-names.typ | typst | Apache License 2.0 | #let degree-types = (
MA: ("文学硕士", "Master of Arts"),
MFA: ("艺术硕士", "Master of Fine Arts"),
MArch: ("建筑学硕士", "Master of Architecture"),
MBA: ("工商管理学硕士", "Master of Business Administration"),
MEd: ("教育学硕士", "Master of Education"),
LLM: ("法学硕士", "Master of Laws"),
MMus: ("音乐硕士", "Master of Music"),
MSc: ("理学硕士", "Master of Science"),
MEng: ("工学硕士", "Master of Engineering"),
PhD: ("博士", "Doctor of Philosophy")
) |
https://github.com/dark-flames/resume | https://raw.githubusercontent.com/dark-flames/resume/main/README.md | markdown | MIT License | # Resume
This is my resume, based on [Typst](https://typst.app) and [Matchy's template](https://github.com/matchy233/typst-chi-cv-template).
## Online Preview
Industry Resume: [Resume](https://dark-flames.com/resume)
Academic CV: [CV](https://dark-flames.com/cv)
Full: [Full](https://dark-flames.com/resume/full) |
https://github.com/Myriad-Dreamin/typst.ts | https://raw.githubusercontent.com/Myriad-Dreamin/typst.ts/main/fuzzers/corpora/text/emoji_01.typ | typst | Apache License 2.0 |
#import "/contrib/templates/std-tests/preset.typ": *
#show: test-page
// These two shouldn't be affected by a zero-width joiner.
🏞🌋
|
https://github.com/jgm/typst-hs | https://raw.githubusercontent.com/jgm/typst-hs/main/test/typ/compute/calc-27.typ | typst | Other | // Error: 11-15 the result is too large
#calc.fact(21)
|
https://github.com/qjcg/typstry | https://raw.githubusercontent.com/qjcg/typstry/main/templates/letter/main.typ | typst | MIT License | #import "letter.typ": letter
#show: doc => [
#letter(
date: "March 23, 2023",
to: "<NAME>",
from: "<NAME>",
body: doc,
)
]
#lorem(70)
- foo
- bar
- baz
- https://example.com/
#lorem(50)
#lorem(60)
|
https://github.com/mangkoran/utm-thesis-typst | https://raw.githubusercontent.com/mangkoran/utm-thesis-typst/main/08_acknowledgement.typ | typst | MIT License | #let content() = [
#align(center)[
= Acknowledgement
]
#v(4em)
I dedicate this template to those who have spent countless hours to make this
possible.
#pagebreak(weak: true)
]
#content()
|
https://github.com/kdkasad/typst-homework-template | https://raw.githubusercontent.com/kdkasad/typst-homework-template/master/examples/english/main.typ | typst | BSD 3-Clause "New" or "Revised" License | #import "../../khw.typ": khw, problem
#show: khw.with(
title: [Example Homework: English],
course: [ENGL 123],
author: "<NAME>",
newpages: false,
problem-name: "Question",
)
#problem[
#lorem(10)
]
#lorem(80)
#problem[
What does this gallery visit (specifically the theater department display) tell you about [institution] and performative arts?
What does it signify about [institution]?
]
#lorem(30)
#lorem(50)
#problem[
How does the gallery help you connect art and your major?
]
#lorem(50)
#lorem(100)
#problem[
What did you like the most about this trip?
]
#lorem(70)
|
https://github.com/polarkac/MTG-Stories | https://raw.githubusercontent.com/polarkac/MTG-Stories/master/stories/024%20-%20Shadows%20over%20Innistrad/005_The%20Mystery%20of%20Markov%20Manor.typ | typst | #import "@local/mtgstory:0.2.0": conf
#show: doc => conf(
"The Mystery of Markov Manor",
set_name: "Shadows Over Innistrad",
story_date: datetime(day: 30, month: 03, year: 2016),
author: "<NAME>",
doc
)
#emph[Jace has come to Innistrad in search of Sorin Markov, one of the three Planeswalkers who imprisoned the Eldrazi on Zendikar thousands of years ago. Despite the dire warnings of Liliana Vess, he has made his way to Markov Manor, ancestral home of the vampire Planeswalker. Without Liliana's help, and with no other leads to pursue, he finds himself on the narrow path to the only place he knows that might offer a hint to Sorin's whereabouts.]
#v(0.35em)
#line(length: 100%, stroke: rgb(90%, 90%, 90%))
#v(0.35em)
Markov Manor was torn apart, opened up and laid out to view like a dissected animal pinned to a board. Spires, halls, buttresses, and turrets were ripped from their moorings and left to hang at odd angles around the sundered core of the manor building.
Jace stood at the end of a long arched bridge that jutted out from the mountainside. Below him was a sheer drop disappearing into mist. Ahead, what was once the rest of the bridge had become a scattering of steppingstones across the void, leading to the entryway of the manor.
"I guess Sorin probably isn't here," he muttered to himself.
Suddenly, he saw the place as it must have once been—an awe-inspiring structure of intricately decorated spires and balustrades, perched like a vulture at the edge of a lofty promontory. His breath caught in his chest as he took in the scale of the...not a manor, no, but a castle. A palace.
And the vision was gone, like an illusion. Scowling, he reached out with his mind, looking for some other intelligence that had forced the image into his mind. No one was nearby, at least not anyone with thoughts he could detect. He reinforced the wards he habitually kept around his mind and surveyed the castle as it actually was.
#emph[Did Sorin do this?] he wondered. Liliana had suggested that he wasn't particularly welcome in his ancestral home. Either way, the sheer scale of the devastation gave him pause. Not for the first time on this journey, he wondered whether he should have taken Liliana's warnings more seriously.
#emph[I should go] , he thought, but it drew him in. Patterns formed and dissipated in the drifting stones, some hint that the pieces of the castle were arranged by an intelligent mind, some promise that there was meaning behind the incredible destruction. #emph[It's a puzzle] , he thought, #emph[and puzzles want to be solved.]
Of course, the first challenge presented by the puzzle was how to reach the manor. A vague pathway of steppingstones did not exactly fill him with a sense of safety. Of course, after the time he had spent clambering across hedrons on Zendikar, the drop didn't trouble him as much as it might have.
He reached his mind out to the nearest stone and prodded it. It barely moved. He couldn't push it hard enough to simulate his whole weight, but this first test had provided encouraging results. Stretching his power a little farther, he pushed the next stone, which bobbed only slightly. A third stone proved completely immobile, though he had to acknowledge that the strength of his telekinesis diminished as distance increased.
It was risky, no question. But he had never seen anything like the castle before him, not even on Zendikar, where the law of gravity was more like a guideline. #emph[Puzzles demand to be solved.]
He stepped off the edge of the bridge and planted his foot on a stone that hung in the air. It sank more than he had expected, and his arms flew out to his sides for balance. He brought his other foot onto the stone and lowered his center of gravity. #emph[All right] , he thought. #emph[I can do this.]
He stepped to the next stone, and the next, and again. Step, step.
And then he was standing on a solid bridge again, and the castle ahead of him was intact and stern, looming over him. He pulled his foot back, unsure for a moment what was solid stone and what was an illusion—or a vision, whatever it was.
He crouched and felt around with his mind again, probing for whatever entity was interfering with his senses. Still nothing, and the vision was gone.
Another step and another, one stone to the next, and at last he was across the chasm.
#emph[I hope I don't have to leave here in a hurry] , he thought.
Looming ahead of him was a towering archway, tall enough that six Jaces stacked head to toe could have fit through. Above and around it crowded a grotesque throng of skeletons, hags, wolves, demons, and things that defied mere names, with a giant vampiric man—the Markov for whom the manor was named, he presumed—overshadowing them all. On either side of him, leering at him, were skulls as tall as he was, and he couldn't be sure whether the whitish stone was actually bone.
He stepped into the archway and the stone walls enfolded him.
#figure(image("005_The Mystery of Markov Manor/01.jpg", width: 100%), caption: [Foreboding Ruins | Art by <NAME>], supplement: none, numbering: none)
My footsteps are echoing in the long passageway, bouncing off the walls high over my head. Is someone following me? I stop and listen for anyone's thoughts. The sound continues—not feet on stone, but my heartbeat, each thump preceded by a softer, smaller one.
Of course. Vampires—naturally, they would have some magic designed to alert them of a living person entering their hall. Like the ringing of a dinner bell.
It's too fast. Deep breaths, Jace. Slow that heart down.
I need a light. I stretch out my hand and cup a blue glow in my palm, concentrating until it's just bright enough to light my way without giving my presence away from too great a distance. On either side of the hallway, tapestries rustle as if a wind is sweeping past them, but I feel nothing. I reach forward with my mind and push a tapestry aside. Only bare wall behind it—another illusion.
As if carried by the nonexistent wind, faint sounds reach my ears—laughter, conversation, maybe music. Limping rhythms in discordant keys. Is it possible this place is not abandoned? More likely I am hearing the spirits of the dead. This plane and its ghosts.
I reach the end of the hall, and the sounds cease. It feels like I've just walked into the middle of a party and everyone stopped dead, turning to stare at me. But only cold stone walls return my gaze.
"Why did you come here?" A voice breaks the silence. My voice—did I speak? My mouth is closed, and I just realized how dry my throat feels. But I was just starting to ask myself...
Why #emph[did] I come here? Because she warned me not to? Because she told me it was dangerous? Because I wanted to stare death in the face and live to tell about it?
"Because you wanted to die?"
I know I didn't say that. Again I reach out my thoughts, probing for the mind behind the words. But it eludes me.
I'm not the first living man to set foot in this hall recently. I see it like a memory—whose memory, though? The castle's? Perhaps the voice is part of the memory. He stands here, terrified, knees knocking, clutching something—a book—to his chest, looking up at...I can't tell. Something over...there.
A door hangs open just a crack there, where the man's trembling gaze fell. Damn it, this place is infuriating! Something is altering my perceptions, pressing in on my mind, and I can't find it. And apparently can't stop it. I missed the door, before, and only noticed it because...someone—something?—wanted me to.
A ghost? If one of Innistrad's geists were drifting through the castle walls, would I know it? I'm not sure whether I would have detected its mind or not. I haven't yet had the opportunity to test that. I'll have to remember to do that, if I should happen to see one.
Perhaps I'm walking into a trap, but I climb the steps and push the door, and it swings open with a metallic wail.
#emph[...have to get out...]
The words spring to my mind unbidden. I didn't think them. Yet I can't detect any other sign of intrusion into my mind—my wards are as strong as ever. Some trick of sound in this place? Or the mind of an ancient vampire Planeswalker, too strong for me to penetrate or to resist? Maybe Liliana was right.
#emph[...to kill me...]
A snippet of thought, a memory. Someone's memory. Probably the living man I saw in the entry hall—or his geist. There's a cold tingle at my spine, which is completely irrational. I ignore it.
My heart-steps echo louder in this smaller passage. Glaring on the stone walls, my light seems too bright. I let it dim and feel the darkness draw closer.
"Why did you come here?" My voice is harsh, too loud. Yes, that was my voice. Talking to myself.
#figure(image("005_The Mystery of Markov Manor/02.jpg", width: 100%), caption: [Clue Token | Art by Cliff Childs], supplement: none, numbering: none)
Option one: something is interfering with my memory.
Option two: I am actually dreaming, in that strange fugue state where you flow from one scene to another with no transition.
I don't remember how I got here. I'm in a grand hall, deeper in the castle now, with wind rushing through the halls around me. Stone grinds against stone as massive fragments of architecture wheel slowly around me. It was once a great vault with soaring columns—now it's a floating field of rubble. With hands, faces, bodies protruding from the stone. Dozens and dozens of them, trapped and petrified and encased in the stone.
"What is happening?" someone shouts. I start, pulling back into the shadows and casting my mind around to find the source of the voice. But it grows into a clamor of many voices, dozens of them, and screams, mingled with raw pain and fury, a glimpse of a white face with fierce eyes—#emph[I will repay...]
And it ends in stony silence.
I turn my head, and I'm face to face with a vampire, mouth open and fangs bared. I actually jump before my brain manages to tell my body that the vampire is dead and embedded in the wall. Embarrassing.
They're all vampires. Heirs, I assume, to the Markov who built this place. They are strikingly inhuman in death: gaunt faces, sunken eyes, jutting fangs, feral features—ugly. One near me is surrounded by a mahogany picture frame with a golden plate at the bottom, except the whole wall is upside down, and the nameplate is far above my head, too far to be read. Tatters of canvas hang from the edge of the frame. I lift the canvas, mindful of the vampire's fangs, and the remnant of the ancient portrait, two red eyes in fading paint, stare back at me. I let the canvas drop—
Did the stone vampire just blink?
I step back and suddenly there are hands all around me, clutching at me. I scream and struggle against the vampires' grasp, but they are too strong. I can feel their hunger in their hot breath, but they wait—and their sire approaches. This must be the one, <NAME>ov, the ancestor of all Innistrad's vampires...
No. This is not happening, not now. The hands clutching at me are motionless stone protruding from the wall, and the approach of the vampire sire is just a memory. The dead man's memory.
It must be his geist, or else some sort of psychic echo of his mind lingers in this place. Perhaps the geist is pushing into my mind, forcing these thoughts on me. Or perhaps it's my own sensitivity picking up the stray thoughts. Or, again, maybe I'm dreaming.
I'm walking. I don't know where to, and I can't remember if this is the way I came. Option one—yes, I considered those.
There are so many dead vampires here. Liliana was right—if I had come here earlier, they'd have torn me apart. I wonder if that's what happened to the man whose memories I seem to be experiencing.
In a narrow hall, I see my own face suspended in stone, horror imprinted on my features.
No, it's #emph[his] face, bearded and blank-eyed. The man from the entry hall. One human amid all the vampires. What are you doing here, you idiot?
He's holding a book.
His stone hands clutch the book protectively to his chest. It's wrapped in blue leather, held shut with a red and green strap of silk. It's out of place here—not just in this castle, but on this plane.
#figure(image("005_The Mystery of Markov Manor/03.jpg", width: 100%), caption: [Tamiyo's Journal | Art by Chase Stone], supplement: none, numbering: none)
A white face, shining like the moon, leans close to mine. Her lavender eyes gleam with excitement as she explains a theory to me, about something she calls "cryptoliths." Is she the one touching my mind? I reach for her mind—she's not there, of course. I feel around again, searching for the intruder—something lurking at the very edge of my awareness?
It's his memory again. The writing in the book—it's a journal—is hers. He couldn't possibly know or understand what she is: one of the moonfolk from Kamigawa. A Planeswalker. It will take a little more time to puzzle out her writing.
I flip to the back of the book, blank pages, and move toward the front until I find the last writing—but this isn't the careful script of Kamigawa. It's written in a different hand, probably his. Jenrik—he wrote his name at the start, when he took over, after she entrusted the journal to him and sent him here.
To his death.
I'm cowering in a secluded nook as the sounds of the vampires' feast drift through the castle, the limping rhythms and harsh laughter. I can't get out. They know I'm here, but they're toying with me, stalking around like cats outside a mouse hole, waiting for me to show myself.
This is tiresome. I might be able to learn something from his memories, but I don't need to feel his fear, his abject terror. My heartbeat has not slowed, and it has grown louder, at least to my ears.
What am I doing here?
"Looking for Sorin," Liliana says. Her voice is too loud for this place. "Looking for death."
"I'm looking for this," I tell her, holding up the journal. But she's not here. Why would she be here?
This is not good. Liliana is mine—she belongs in my mind. Somebody pried her out of my mind and used her voice against me. How is this happening?
Option two, that I am dreaming, seems increasingly likely. I would like to awaken now.
"You should go," Liliana says. I should go.
I can't get out.
I climb the stairs with their plush red runner, back the way I came, and push open the door at the top. Howling winds blow up over and around me and everything spins. My arms flail in empty air and I stare down into the misty depths below, sure I'm going to fall, until my hand catches the doorjamb and I pull myself back.
This is not the way I came. Obviously.
Something is interfering with my memory. I thought I remembered coming down the stairs to the great hall—perhaps that was Jenrik's memory as well. I need to sift through, sort out which memories are his and which belong to me, but I feel like I don't have time for that.
Interesting. Why do I feel so rushed, in this apparently empty castle? Checking yet again—I can't find another mind, but the sense of urgency only intensifies. Just some strange effect of the place, I suppose, deserving of further study...some other time.
Huge double doors stand partly open in the vampire-studded walls. Did I come through that way? Inside is a space like a chapel. A sculpture, similar to the relief that towers over the castle entrance, dominates one whole wall. Again the master vampire stands over the scene, carved into the wall, only this time he is more human, less...inhuman bloodsucker, I suppose. Others stand around him—some carved into the wall, some half-emerging like the once-living vampires in the great hall outside, and some freestanding, with their backs to me. They're dressed like aristocracy, but there is a hungriness to their poses. The dozen of them circle an altar where an angel lies bound, straining against the ropes as the master holds a knife, poised to open her veins.
Drinking an angel's blood in some kind of ritual—it seems like a recipe for something horrific. If <NAME> really is the first vampire of Innistrad, and if that's him holding the knife, I wonder if I'm witnessing the birth of the vampire race on this plane.
The knife slashes and glowing silver blood erupts from the angel's neck. The twelve draw closer to feast—Edgar first, catching the blood in a silver goblet before drinking it. I can only watch as the life slowly drains from the angel and new life takes root in the perpetrators of this crime.
Wiping her chin, one of the twelve looks over her shoulder at me. Either she is inviting me to join the circle, or she is planning to drink my blood next. In any case, I stumble back out of the room, a final glance over my shoulder confirming that the vampires have returned to their motionless poses.
I need to go. I can't get out.
My feet take me to another hall. It looks familiar.
"Why are you here?" I hear again. Is it Liliana's voice? No, my cracked lips sting from forming the words.
"I came for this," I say again, fingering the book.
"What's so important about that book?"
I don't know. I open the book and look through the pages for an answer.
#figure(image("005_The Mystery of Markov Manor/04.jpg", width: 100%), caption: [Pore Over the Pages | Art by Magali Villeneuve], supplement: none, numbering: none)
An angel's face stares back at me. Is she judging me for not intervening to stop the vampires' ritual? Idiot. She's a drawing in a book, and that was—an illusion, a vision, or a memory drifting through this place. An old, old memory.
Beside the drawing is another sketch, showing one of the weird, twisted stones I've seen a few times since I've been here. There's a schematic quality to the sketch, and I wonder if the author of this journal is responsible for the stones. There's magic in them, manipulating mana flow.
But I puzzle out the words on the page; they're about the angel, Avacyn. Clinical and carefully lettered, as if to underline the weight of the words: Sorin made her. Sorin wanted to protect the humans of Innistrad so the vampires wouldn't overfeed on their blood. Innistrad's incarnation of purity and goodness was manufactured by a vampire Planeswalker to maintain the balance between powerful predators and helpless prey.
Angels—Liliana mentioned angels, suggesting that they're even worse than the werewolves that attacked me. I took it as just another one of Liliana's snide remarks. She never did like angels. But the writing is suggesting something else.
"The angels have gone mad." My dry throat croaks in the echoing hall.
<NAME> made Avacyn. Avacyn ruled the angels. The angels have turned on the human populace. And someone tore Markov Manor to pieces.
Option one: Sorin has gone on a rampage, destroying his ancestral home and turning his angelic creation against Innistrad's people.
Option two: someone has challenged Sorin, destroying his ancestral home and turning his angelic creation against Innistrad's people.
Both options are slightly terrifying. But either one would explain Sorin's absence from Zendikar. And either option points to the angels as a way to find Sorin. And this book explores the madness of the angels. Closing it and clutching it to my chest, I say to no one, "This will help me find Sorin."
As soon as I get out of here.
The next hall is familiar, and I know where to go. It all makes sense, more and more with every step I take away from the heart of the castle: the place is full of psychic residue, snippets of memories both recent and ancient. Jenrik came to the castle carrying the journal, but as the vampires were about to catch him and feast on him, someone ripped the castle apart and trapped the vampires—and poor Jenrik—in the walls.
Here's the entry passage. I take one last look behind me:
So, so dark. And I feel a presence in the darkness, a hunger, a desire. But still no mind. I reach out and feel...nothing at all. A void.
I turn my back on the darkness, pass through the soaring entryway, and leave Markov Manor.
#figure(image("005_The Mystery of Markov Manor/05.jpg", width: 100%), caption: [Jace, Unraveler of Secrets | Art by <NAME>], supplement: none, numbering: none)
|
|
https://github.com/syrkis/esch | https://raw.githubusercontent.com/syrkis/esch/main/requirements.typ | typst | MIT License | #import "@preview/touying:0.5.2"
#import "@preview/lovelace:0.3.0"
#import "@preview/equate:0.2.0"
|
https://github.com/refparo/24xs-zh | https://raw.githubusercontent.com/refparo/24xs-zh/master/adventure4-suit.typ | typst | #set document(
title: "24XS 微型单人冒险：紧身衣",
author: ("<EMAIL>", "diceghost.itch.io", "Paro")
)
#include "rules4.typ"
#import "common.typ": *
#show: typ-24xs
#adventure-page(
[
*冒险*：送来一个包裹，里面是一件微型紧身衣和一张便条：“#underline[他们随时会到达。]”紧身衣被你触碰瞬间就扩张到你的尺寸。你一穿上它就不可逆地变小。外面传来一声巨响。快逃！\
*选或者编 2 个技能*：飞行，穿过物体，提升密度，昆虫交谈，发射火花，表面附着，巨力。
],
random-table(
[要恢复正常大小你必须……],
[在屋顶接收信号],
[到处收集科技],
[到达街对面的微型货车],
[找个交通工具穿过小镇],
[击败袭击者——这是试炼],
[解密一串奇怪的线索],
),
random-table(
[这时你发现……],
[大楼被纵火了],
[你还在缩小，只是很缓慢],
[赛博忍者在搜寻这件紧身衣],
[衣服出了故障，不停地激活能力],
[房间里飞满了机器蜜蜂],
[你不是唯一一个有这种紧身衣的],
),
random-table(
[出去的唯一一条路上有……],
[古老居家蜘蛛的巢穴],
[飞速流动的水流],
[贪吃宠物的大嘴],
[故障电器的火花],
[裂口吹进的强风],
[人们脚步的震动],
),
)
|
|
https://github.com/gabrielluizep/klaro-ifsc-sj | https://raw.githubusercontent.com/gabrielluizep/klaro-ifsc-sj/main/README.md | markdown | MIT License | # klaro-ifsc-sj
A report Typst template for [IFSC-SJ](https://sj.ifsc.edu.br/).
## Usage
You can use this template in the Typst web app by clicking "Start from template"
on the dashboard and searching for `klaro-ifsc-sj`.
Alternatively, you can use the CLI to kick this project off using the command
```
typst init @preview/klaro-ifsc-sj
```
Typst will create a new directory with all the files needed to get you started.
## Configuration
This template exports the `report` function with the following named arguments:
- `title`: The reoirt's title as string. This is displayed at the center of the cover page.
- `subtitle`: The report's subtitle as string. This is displayed below the title at the cover page.
- `authors`: The array of authors as strings. Each author is displayed on a separate line at the cover page.
- `date`: The date of the last revision of the report. This is displayed at the bottom of the cover page. |
https://github.com/polarkac/MTG-Stories | https://raw.githubusercontent.com/polarkac/MTG-Stories/master/stories/024%20-%20Shadows%20over%20Innistrad/001_Under%20the%20Silver%20Moon.typ | typst | #import "@local/mtgstory:0.2.0": conf
#show: doc => conf(
"Under the Silver Moon",
set_name: "Shadows Over Innistrad",
story_date: datetime(day: 02, month: 03, year: 2016),
author: "<NAME>",
doc
)
#emph[Halana and Alena are trackers, hunters, and protectors who live in the depths of the dark woods that border the edges of Kessig province—the woods known as the Ulvenwald. Innistrad's ancient forest is their domain, and they have long stood as a bulwark between the horrors within and the innocence without. But of late, things in the woods have begun to shift...]
#v(0.35em)
#line(length: 100%, stroke: rgb(90%, 90%, 90%))
#v(0.35em)
"You know that feeling? That crawling feeling?" Farmer Warin was standing in front of the long table of Elders, his plump, wide-eyed wife at his side. Both had turned their backs to the Elders in favor of addressing the Gatstaf townsfolk gathered in the cramped parish commons. Halana looked on from the seat closest to the door, where she sat next to Alena.
"It's like a beetle is crawling up the back of your neck." Warin shuddered as he spoke. "Right up from the base of it and straight into your hair."
#figure(image("001_Under the Silver Moon/01.jpg", width: 100%), caption: [Art by Nils Hamm], supplement: none, numbering: none)
It was odd, Hal thought, that he should speak of that feeling now, today. She had never heard mention of such a thing before, never known such a sensation was possible, not until this very morning. She had woken with it, something ticking on the back of her neck, crawling up her spine. It had made her feel unsettled, which in itself was extremely peculiar. So the fact that the feeling, which had crept after her out of their bed at camp through the woods and into town, should be brought up again so soon after she first felt it was enough of a strangeness to dredge up another wave of it. She suppressed a shudder of her own.
"It's so real that you have no choice but to wonder if something's really there, you know?" Farmer Warin itched the back of his neck furiously. Seeing him do so made Hal realize she was doing the same. She clasped both hands on her lap. "Something horrible could be burrowing under your skin and you'd never know it!"
Many a townsfolk twitched and shifted in their seats, itching along with Farmer Warin.
"Yes, yes," Elder Kolman waved his thick hand as though shooing away a fly. "We all know the feeling, Warin, but what's it got to do with why you've come here today before the council?"
"Everything!" Farmer Warin turned back to face all eleven of the elders present—they were down from their usual twelve, as Elder Somlon was absent due to her performing the second day of death rites to see good Lady Mary into the Blessed Sleep. "That crawling feeling is how I know I'm right!"
"Right about what, Warin?" Elder Kolman prompted.
"Spit it out already!" Elder Glather hollered.
"One of our cattle is possessed!" Farmer Warin's wife seemed unable to contain herself. "Gone mad! In the middle of the night. And it ate the other one! Dragged it all around the pasture first, though. I saw the tracks myself. The pain the poor animal must have endured. Then the mad one just devoured it. It left nothing behind but the bones and teeth."
There were gasps from the townsfolk.
"And how do you know that it was the first cow that ate the second?" Elder Kolman asked, feigning patience.
"I saw the blood on its own snout this very morning!"
More gasps.
Hal looked to Alena. Communication between them required no words. They both knew that the Warins' farm was situated at the edge of town. They both knew it abutted the woods of the Ulvenwald. And they both knew what beasts had, of late, made a fateful resurgence in their forest. In the span of a fortnight, Alena and Hal had each on their own dispatched three lycanthropes, and in addition, together they had taken out a whole pack—small, but certainly a pack—just the night before. But those encounters had all been far enough from Gatstaf to not raise concern, Hal having followed a distant howl halfway down the Bower Passage, and the one Alena had taken was out at the Natterknolls. But now their shared look said there was reason to believe the beasts had become brazen, that they were working their way to the fringes of the woods, to the towns, to the people. That was unacceptable. The Ulvenwald was Alena's and Hal's domain, and they would not let its dark horrors leak out to harm the innocent.
"Our wards!" Wife Warin's wail drew Hal's attention back to the front of the room. "#emph[She] made our shoddy wards!" The farmer's wife thrust an accusatory finger in the direction of good <NAME>, who gasped and clutched at the ward at her neck. "She made them, and they failed!"
"It couldn't have been the wards!" The man seated at Evelin's side jumped up to her defense. "L<NAME> makes the best and most potent wards this town, nay, this land, has ever seen!"
"Order!" <NAME> shouted, pounding his thick flat hand on the table of elders. But he was ignored.
"Then how do you explain the possessed cow?" Wife Warin challenged. "The tracks that show it dragged the other around our farm? The bones it left behind after feeding?"
"Aye!" someone shouted from the back.
"The wards didn't do their work," came another voice.
"There can be no doubt, the wards failed, and our cow was possessed." <NAME> seemed to have gathered courage to speak from the rallying of so many townsfolk to his cause. "We are the victims of Lady Evelin's neglect." He held tight to his own ward and beseeched both the townsfolk and the Elders. "We cannot afford to go one more night without a proper ward."
#figure(image("001_Under the Silver Moon/02.jpg", width: 100%), caption: [Art by <NAME>], supplement: none, numbering: none)
There was a rabble of agreement.
It made sense to Hal that the townsfolk would blame it on faulty wards. That they would think their cow possessed by an evil spirt. These were things they could define. These were things they had the means to put right. Things that did not upset the careful balance that they believed to govern their world. They did not live in the same reality that Hal and Alena did. The townsfolk didn't see what happened in the darkness, in the woods. They lived in a world protected by the light of the angel Avacyn. They believed themselves safe from things like werewolves. But even in Avacyn's world, the werewolves were never completely wiped out. Lycanthropes had had a constant presence in the Ulvenwald, significantly diminished though it was. Hal and Alena would know. They had heard the lycanthropes' unearthly howls echoing off the trees, a permanent fixture in the forest's deepest reaches.
Thinking of their howls, Hal shifted uncomfortably in her chair; the crawling feeling returned to the back of her neck. A howl was what she had heard, what had brought on the unwelcome feeling in the first place. She had first thought she had dreamt it. The fight earlier that same night with the pack had been playing out in her dreams. It had been some time since she and Alena had faced a pack. It had also been some time since they had faced so many lycanthropes in such a short span. Hal had been seeing flashes of their muzzles, their muscles, their haunches in her mind as she had laid in bed, so she had not been surprised that she woke thinking that she had heard a howl.
But now, looking at the bulging eyes of Wife Warin's face, she worried that the howl had not been in her head, had not been a memory nor a dream but the sound of a real and true beast. The very beast, in fact, that had dared to come into the town, had dared to feast on the Warins' domestic cattle. It would not be allowed to do so again. "Shall we?" Hal silently mouthed the invitation to Alena.
Alena's face lit up, the glow of the hunt already upon her.
Together they rose. Hal's fingers tingled in anticipation, her eyes on the handle of the nearby door—the door that in the next instant flew open.
Innkeeper Shoran and his wife, Elsa, charged into the parish hall.
"Ring the town bell!" Elsa cried.
"She's gone," the innkeeper said.
"She's dead!" Elsa amended. "He killed her!"
Any order that <NAME>man had succeeded in restoring in the last moments went out the window. The townsfolk howled and shrieked and jumped to their feet.
"Oh, the poor girl," Elsa wailed. "The blood was all over. I can't imagine what he did with her body. I knew he was a depraved and wicked man, I knew it from the moment they came to the inn, from the moment they came to town#emph[.] "
"The Palters," Hal whispered to Alena.
Alena nodded in confirmation.
It was obvious who the victim and accused were supposed to be: the Palters from Gavony. They were currently the only guests at the inn, the only guests the inn had seen in the last three months. Hal and Alena had found the cathar and his wife themselves no more than a week ago, wandering the deep paths of the Ulvenwald up near Bower Passage. Of course Hal and Alena had helped them, of course they had seen the two out of the twisted wood and to Gatstaf, fighting off no fewer than three wolves, one ghoul, and a possessed oak on the way.
#figure(image("001_Under the Silver Moon/03.jpg", width: 100%), caption: [Art by <NAME>], supplement: none, numbering: none)
Hal smiled at the memory of Alena's swift dispatching of the tree. The highly skilled tracker had improved her grappling skills so significantly over the past year that Hal wouldn't be surprised if she could take down a giant skaab without any sort of outside assistance.
The Palters had thanked Hal and Alena in kind, or at least Mr. Palter had, for his wife had been so shocked by the trials of traversing the dark wood that her slender form had retreated entirely under the hood of her riding cloak. Mr. Palter, who explained he was a cathar of the Lunarch Council, insisted on giving Hal and Alena a token of protection, one that he had used many times, he claimed, to help him in his duty as guard of the mausoleum. Hal and Alena had taken the token politely, but it meant little to them, for they did not believe in the need for such things—not when they had each other.
"Ring the bell!" Wife Shoran commanded once more. "There is a murderer on the loose in our town!"
Hal would not have thought the Palters, either one, to be a murderer. The cathar was kindly, and his wife most obliging, if slightly fragile. Could it be that this too was the lycanthrope? It certainly seemed so.
"Come on," Alena hissed, gesturing toward the door, which was no longer barricaded. The two innkeepers had moved farther into the fray, embraced by the folds of townsfolk who were hungry for further details of the gruesome happenings.
Hal and Alena slipped easily through the crowd without drawing attention. They were well practiced at moving by stealth, and in two quick, lithe strides they were out the door and on the cobbled street.
"So it—" Hal began.
"Or they," Alena said.
"Yes, or they," Hal amended. "This could have been the work of a pack. Another pack..." she mused. "That would make two packs that were in relatively close proximity in one night. That hasn't happened in some time." She cast a glance at Alena, who did not look back, so focused was she on their heading. "Either way," Hal went on, "the lone lycanthrope or the pack attacked within the boundaries of Gatstaf at least twice last night. Once the cow at the Warins' farm."
"And once Mrs. Palter in the Shorans' inn."
Hal abruptly halted in her tracks, and her hands flew to cover her gaping mouth. Her mind had just put something together.
"What is it?" Alena asked over her shoulder.
"It's shocking, to be sure." Hal hurried to catch up. "But where the townsfolk are far off in their assumption of the possessed cow, they are not so far off at all in properly identifying the one responsible for Mrs. Palter's murder."
Alena cocked her head in question.
"In the inn," Hal repeated Alena's own words back to her.
"In the inn..." Alena said. Hal could see the work of her mind behind her eyes. "...In the Palters' room...behind a locked door."
"With no mention of a broken window or forced entry," Hal said.
As one, they changed course, running for the Shorans' inn.
#v(0.35em)
#line(length: 100%, stroke: rgb(90%, 90%, 90%))
#v(0.35em)
The tolling of the town bell continued, far past the point of being any useful sort of alarm.
#figure(image("001_Under the Silver Moon/04.jpg", width: 100%), caption: [Village Bell-Ringer | Art by David Palumbo], supplement: none, numbering: none)
From the sound of it, Hal thought it likely that <NAME> herself had come into possession of the rope, having most likely wrestled it from the hands of the bell-ringer. If that was the case, then all the better; the distraction Elsa was most likely providing to the Elders, who would be left, in turn, to wrestle the rope from her hands, would afford Hal and Alena more time to search the Palters' chambers.
They made their way past the desk in the reception area and stalked down the hall. Hal nodded ahead to the only door that was left ajar, no doubt by the harried innkeeper and his wife after having witnessed the scene of a murder. Hal moved into the room first and Alena followed; neither disturbed the angle of the open door.
The metallic scent of blood hit the back of Hal's throat on her first breath. "This way," she whispered, winding past a toppled chair in the small foyer and back toward the dimly lit bedroom. She sensed Alena tense. Though the candles were snuffed and the curtains drawn, there was enough light for them to see the pool of dark blood on the floor. Alena, Hal knew, had not tensed out of fear; she wasn't the kind of girl to become afraid at the sight of blood. The stillness was her way of focusing her senses. Hal had learned much of her own skill in tracking from studying Alena. She imitated Alena now, becoming motionless so that she could be more sensitive to the clues around her. Looking at the vast dark pool, her thoughts turned to the slight woman whose blood this was. Hal only let her mind dwell there for a moment, and for that moment she allowed herself to feel pain and pity for the woman. Mrs. Palter was an innocent who had lost her life to one she so trusted. Hal glanced up at Alena. How terrifying those last moments must have been. How awful the realization. But she could not dwell on the feelings of sorrow. It would do no good in the work they had to do next.
Careful not to disturb so much as a drop of blood, Hal stalked the perimeter of the small, square room, moving about it clockwise as Alena moved in the opposite direction. Three clues presented themselves without hesitation: a torn bit of lace, a toppled candle lying in a puddle of its own hardened wax, and a silver button. It was the button that held Hal's attention. As she came round the perimeter to meet Alena again, she pointed to where it lay on the floor near the pool of blood. "Tell me if I am mistaken," she said. "But wasn't <NAME> wearing a green vest with three buttons just such as that one when we met him in the woods?"
Alena's look was somber. "Your memory is accurate as always, I fear."
"Then it is true," Hal said. "His transformation occurred in this room. He killed his own wife and then fled, through the Warins' farm, snacking again, and then into the woods."
"Yes, so it seems," Alena said. But Hal could tell by her voice that she wasn't convinced, not entirely.
"What is it?" Hal asked. "What has caught your eye?"
Alena gestured to the pool of blood. "I cannot help but wonder: the blood is here, so much of it on the floor, but what of the bones, the bits of flesh, the hair and fabric, the things the beast would not have devoured?"
Hal stepped back, taking in the scene with fresh eyes. Alena's was an important question to ask. But before Hal's mind could settle into answering it, something else claimed her attention. Behind Alena, the door of the closet was cracked just enough for Hal to make out what was inside. At the sight, Hal's heart quickened. Alena noticed immediately. Her brow furrowed in question and she turned to look over her own shoulder. They both stood staring for a long moment. In the closet was a chair. It was an ordinary enough chair besides the fact that it was sitting in the closet. But that in itself wouldn't have been enough cause for concern, and that had not been what had sent Hal's heart to hammering in her chest. It was the leather straps and belts that hung from the chair, more than a dozen, of all lengths, ripped and shredded, that had given her pause. And there were three locks, one on the chair's seat and two on the floor.
"That seals it then," Alena said.
"He knew," Hal said.
"Of course he did." Alena's voice was sharp. "We must stop him. We should—"
But she never finished her thought, because in one fluid motion Hal wrapped her arm around Alena's midsection, drawing the girl to her breast and pulling her into the shadows. Together they stood still and silent. They were so well practiced in this form of concealment that their breaths instinctively fell into sync, low and shallow, difficult even for the most astute of creatures to detect.
It had been the silence that had alerted Hal. Or at least the lack of the clamoring noise, which had been sounding continuously up until that point. The bell was no longer ringing. That would mean that the murder investigation was on. The din of echoing footsteps and muffled voices confirmed it; the townsfolk were headed to the scene of the crime, to the very room where Hal and Alena were now pressed into the corner.
The creaking of the door to the inn said to Hal and Alena that they could not go out the way they had come, at least not without needlessly rousing suspicion. As a rule, they avoided run-ins with the townsfolk whenever possible. The townsfolk tolerated Hal and Alena. They accepted the presence of the trackers in Gatstaf whenever the two came to town because they had aided visitors and townsfolk alike on their journeys through the Ulvenwald. But at the same time, the townsfolk knew that Hal and Alena lived in the dark woods, and for that reason they were considered "other." Glances were cast, suspicions shared in hushed voices, and prayers uttered in passing. Hal sensed as much fright as dislike on the scents of those to whom she came too near. It would do no good to be found at the scene of a murder.
Alena nodded to the window in the back of the bedroom, the one that opened into the alley. Perfect. Hal smiled at Alena's ever-dependable adeptness at getting them out of tight situations. On their way out, Hal carefully and quietly closed the door to the closet. There was no reason for the townsfolk to see the thing that would so rattle and upset them. No point in stirring up such worry that would surely come with even the barest hint of the presence of a lycanthrope. The people need not believe they were being hunted, for they were not. Hal and Alena would handle this. They would protect the innocent. The Ulvenwald and its threats were for them to manage. And they would.
They timed the opening of the window with the banging open of the outer door to the room. The sliding of wood over wood as they closed the window was then drowned out by the thumping of heavy boots and competing baritone voices as the Elders and other townsfolk flooded the room. Hal and Alena climbed down into the alley without any of the townsfolk being the wiser.
#v(0.35em)
#line(length: 100%, stroke: rgb(90%, 90%, 90%))
#v(0.35em)
They hadn't much time. The sun was already kissing the horizon when they arrived back at their camp deep in the Ulvenwald. Each quickly but deliberately strapped on her silver. Of course they always carried one small blade of it—it would be foolish to be completely unprepared—but until recent events there had seemed no need to carry more. Now they found both the need and means to carry nearly all of it with them: silver-tipped arrows, swords, spears, and daggers. The metal gleamed with power.
#figure(image("001_Under the Silver Moon/05.jpg", width: 100%), caption: [Silver-Inlaid Dagger | Art by Austin Hsu], supplement: none, numbering: none)
As soon as they were equipped, they left their camp again. Moving as one, they navigated the maze of brambles Hal had planted around their home as a safety measure and pressed out into the darkening woods.
Alena was first to pick up on <NAME>'s trail. She was often the first to get a scent. Her nose, though petite and perfectly round in a way that set her whole face alight when she laughed, was also sharp and discerning. Her skill was well-honed. Hal found the scent only moments later, recognizing it from the room of the inn, and saw the boot prints an instant after that. Together they stalked the murderous lycanthrope.
His tracks wound around the twisted trees, seeming to say either that he was lost, or more likely that he was struggling with himself, with the animal that he was inside. Hal imagined that same struggle was what had driven him to pick up his life and leave Gavony. He must have killed there. Most likely more than once. And when he had realized the horrors he had committed, he doubtless had no longer been able to face the people whose lives he had affected. So he had fled. It wasn't odd behavior. Not for a lycanthrope. What was stranger was bringing his wife along with him. The poor soul. Hal could not reconcile that behavior with the impression of kindness and compassion she had gotten from Mr. Palter when they had found the couple in the woods. She wished to give the cathar the benefit of the doubt. Perhaps he had intended to leave <NAME> in the safety of a new town, away from any suspicions that might be cast her way because of his actions, somewhere that he could believe her to one day start anew and find happiness. Then maybe he planned to sequester himself to the wood, or worse. She imagined that's what she would do, if ever the curse was transmitted to her—perish the thought—she would not, she could not, put Alena in danger. She would leave. She would have no choice but to go very, very far away. And she would do so, all the while, knowing that her heart would never mend. Perhaps the act in itself would be enough to stop her heart from beating altogether. What a mercy that would be. If that is what <NAME> had tried to do, Hal felt nothing but the deepest sympathy for him. That is, until the next moment when she thought of Mrs. Palter's blood on the floor. Regardless of his intentions, <NAME> had failed the one he loved. He had not been strong enough, and his shortcoming had resulted in the end of her life.
As though in response to Hal's shifting feelings toward the cathar, his tracks shifted too. It became clear when his transformation had taken place, for one moment Hal and Alena were following the boot prints of a man and the next they were tracking the paw prints of a beast. They moved along the lycanthrope's path until abruptly and unexpectedly they came to a crossroads. Hal and Alena eyed the split trail at their feet, visible thanks to the light of the silver moon.
#figure(image("001_Under the Silver Moon/06.jpg", width: 100%), caption: [Paraselene | Art by <NAME>], supplement: none, numbering: none)
From the point where they stood, <NAME> had gone two different directions, surely at two different times. He must have gone one way first and then at some point, near or far from this point of intersection, it was hard to say, doubled back and gone the other.
"East to Gatstaf or west to the deep woods," Alena said. "It seems our beast was fighting an inner struggle."
Hal nodded. It did not surprise her that though she had not vocalized her theory, Alena's mind and landed in the same place. "So," Hal said. "Which way did he go first? Where is he now?"
"Did he let his cravings drive him to town, and then at some point retreat?" Alena looked into to the wood.
"Or did he try to overcome, only to be driven back to town by his cravings?" Hal looked to the town.
"We have to—" Alena began.
"Go to the town," Hal finished.
They ran.
The point at which the tracks emerged from the Ulvenwald was at the edge of the Warins' farm. That was unsurprising. Lycanthropes were known to return to feeding grounds that had proved fertile in the past. But Mr. Palter had not fed here this night, at least not yet. The proof of it was that one of the Warins' two cows remained standing far to the side of the field, its back toward the tracks in the pasture, which Hal could make out now in the light of the moon. They were as Wife Warin had described, thick and curved as though a heavy body had been dragged over the tall grass, round and round, compressing the blades beneath it as it went. The sorry animal.
Hal wandered into the tracks, tracing the path the lycanthrope must have taken. This was strange work for one so bestial in nature. Why not just feed? Perhaps he was fighting his urges even then. A picture of who <NAME> was began to form in Hal's mind. He was a good man, a kind man, a man of the church. His intentions, it seemed, were in the right place, even when he was not of his right mind.
"I've lost his scent completely." Alena's words brought Hal back to herself. As she joined Alena in a search to pick up the lycanthrope's trail, she reminded herself that intentions were nothing without action. She and Alena would have to kill the werewolf.
"Murder! There's been a murder!" <NAME>'s voice echoed through the night. "It's the bell-ringer! Oh, poor Orwell is dead!"
Then came the ringing of the bell. The rope once again pulled by L<NAME> herself, no doubt.
Alena and Hal wasted no time; before L<NAME>sa's voice had ceased echoing, they were moving through the night like two shadows. Concealed in the dark alcoves, they closed in on the press of townsfolk who had gathered round the bell. Careful, silent posturing allowed them to see through the mass of shoulders and necks to the pool of dark blood on the ground at the base of the bell tower. There was no mistaking the pattern. This was the work of Mr. Palter. The lycanthrope had killed again.
As though in confirmation of Hal's conclusion, a howl sounded from the Ulvenwald. Without a word, Hal and Alena took flight toward the woods. But before they were out of sight of the square, Hal glanced back over her shoulder. Something about the scene niggled at the back of her mind. However, there was no time to wonder what it was. She turned back toward the trees; they were on the hunt.
Entering the wood through the Warins' farm, it was easy to pick up the large, lupine tracks again. They followed the trail past the point where it diverged, this time moving west, deeper into the forest. Hal realized where they were headed: the henge of old Avabruck, the lost capital. It was a place of geists and werewolf scavengers. Perhaps they would face more foes than just the one they were pursuing. As she ran, Hal touched the hilt of her favorite dagger, ready to defend her woods.
#figure(image("001_Under the Silver Moon/07.jpg", width: 100%), caption: [Forest | Art by <NAME>], supplement: none, numbering: none)
Suddenly, Alena held up her hand and ground to a halt. Hal nearly trampled her, but managed to stop just before colliding, her eyes on the sight that had given Alena pause. There before them on the forest floor was the body of the bell-ringer. Orwell was ghostly white, his skin withered for lack of blood in his body—a body that was for the most part intact. His limbs were splayed out as though they had been carefully arranged. And all around him the underbrush and grass had been tromped down as though something heavy had been dragged over it.
Something was not right. There should not be a body. The beast should have fed.
Senses on high alert, Hal and Alena stalked the scene, Alena at the perimeter and Hal along the path of dragging. She knew it before she paced it out—the shape of it, the look of the curves, it was the same shape as the marks in the pasture at the Warins' farm. This made no sense. Was this the result of some sort of ritual? Was this tracing of a pattern something <NAME> did to resist the urge to consume? What kind of lycanthrope were they dealing with?
Hal looked to Alena to ask that very question, but Alena's eyes were glued to a place further on into the woods, barely lit by the light of the moon. Hal followed Alena's gaze and saw it too: a second body. When they approached, they found that the same that had been done to the bell-ringer had been done to the ward-maker, <NAME>, appendages splayed, grass beat down. And just beyond was the body of Elder Somlon. Again, the same pattern in the grass, the same arrangement of the arms and legs.
"Elder Somlon was to have been—" Hal began.
"Seeing to death rites." Alena finished.
"But then, she must never have been given the chance. Look." Hal pointed to a detail that made her hand tremble. It was the lace of Elder Somlon's blouse. It matched the bit of lace that had been left behind in the Palters' room at the inn. And there, at the cuff of the Elder's sleeve, they could see the gap where the bit they found would have fit.
"If <NAME> was the victim at the inn," Alena said.
"If that was her blood," Hal added.
"Then what of <NAME>?"
The crawling feeling returned to Hal, this time running straight up from her tailbone to the top of her skull. The shiver that passed through her was augmented by the vibrations of the howl that rang out at that very moment in the night.
"And what of <NAME>?" Hal asked.
"I believe it's time to find out," Alena said. She darted off in the direction of the howl and Hal followed.
As they ran, Hal noticed that they were moving parallel to another's trail. She adjusted her heading to align herself with the tracks. They were boot prints. <NAME>'s boot prints? Something in Hal's mind clicked.
"What is it, Hal?" Even through the trees, even at a sprint, Alena had sensed the shift in Hal.
"The moment of transformation." Hal's mind was racing along with her feet, putting together pieces, struggling to find an answer to a question that she didn't know how to ask. "If it happened there," she panted, "back in the woods—"
"It did," Alena said between heavy breaths. "We both saw the proof of it. His human prints and then the lupine ones."
"No." Hal shook her head. "We saw boot prints. And we saw paw prints. Separately."
"Yes," Alena said, impatient.
"But if they were from the same feet," Hal went on, "then where were the boots themselves?"
Alena slowed in her gait, almost imperceptibly, but Hal noticed it; she had the girl's attention. Hal pointed to the ground at her feet. "And why do we see boot prints again here?"
Alena stared at the ground as they ran, taking in the sight of the boot prints.
"What if," Hal began when she believed Alena to have had enough time to put the pieces together herself.
"It is not Mr. Palter?" Alena finished.
"What if the lycanthrope is—" Mrs. Palter's name was caught on Hal's lips because in the moment she was about to speak it, they had crested a hill, from the top of which they were able to see a small clearing. And in that clearing there was what looked to be a makeshift altar made of twisted stone.
#figure(image("001_Under the Silver Moon/08.jpg", width: 100%), caption: [Art by <NAME>], supplement: none, numbering: none)
The altar was uneven and poorly constructed, and atop it lay the good <NAME>.
Standing behind him, her hood pulled down over her face, as it was when they had met her for the first time in this woods, was Mrs. Palter. Her arms were raised above the body of her husband, and she was chanting. It was demonic chanting. Hal recognized the intonations and deep guttural sounds. "Ormendahl. Ormendahl! ORMENDAHL!" The name was clear. This woman was in contract with a horror.
"Bes, please." Hal's heart lifted upon hearing the weak voice. Good Cathar Palter was still alive!
"Be silent!" His wife spat. She drew a blade.
Hal and Alena both lurched forward, racing toward the small clearing. Mrs. Palter looked up at the sound of their approach, but only in time to glimpse their forms as they tackled her to the ground.
Though her body bucked and her arms thrashed with more strength that Hal had previously given her credit for, they managed to hold her pinned. Alena drew her own blade.
"No!" <NAME> cried from atop the altar. "Don't hurt her!"
Hal glanced up at him. "She was trying to kill you."
"Let her go. Please. She doesn't know. Oh, she doesn't know what she's doing."
"It was her, wasn't it?" Alena asked, holding her blade to Mrs. Palter's neck. "She killed them. All of them."
The cathar did not deny it.
"The blood in your room at the inn that morning, that was Elder Somlon's blood, wasn't it? You knew what she was capable of when you left Gavony, when you brought her to Gatstaf. You tried to bind her, in the closet, but the straps could not hold the evil that possesses her." Alena offered one damning truth after another. "And then she got out. She tried to kill at the Warins' farm; she etched her demonic markings into the ground, but you stopped her. However, after that, you lost control. You followed her around the town, unable and unwilling to stop her from collecting her victims, so instead you brought them here. To hide them, to hide her. One after another, you moved the bodies. Three bodies, Mr. Palter. She killed three innocents."
"It's my fault!" <NAME> wailed. "It's all my fault! The mausoleum was under my guard. Whatever emerged from it that night, I could have stopped it."
Hal doubted that very much. The demon's name, Ormendahl, she had heard it before. And from the stories she knew of it, it was not a demon that a single mausoleum guard, no matter how good-hearted and well-intentioned, could have stopped.
#figure(image("001_Under the Silver Moon/09.jpg", width: 100%), caption: [Art by Min Yum], supplement: none, numbering: none)
For the third time that night, her heart went out to Mr. Palter. But her sympathy for him was not enough for her to consider letting Mrs. Palter free, for the woman was lost; what was left writhing under Hal and Alena's grip was not Mr. Palter's wife. That would be an impossible thing for him to understand. Hal nodded to Alena, who readied to plunge her blade. But just then, <NAME> half-fell, half-launched himself off the altar, his body crashing into Hal and Alena.
In that instant, their shared grip was loosened just enough for the cursed woman to free herself. Mrs. Palter leapt to her feet, and Hal could feel the power collecting within the slender waif of a woman. Then Mrs. Palter opened her mouth wide and roared down at Hal and Alena. The sound was not unlike a werewolf's howling. Something gripped Hal's mind as she and Alena sprang for the woman. #emph[What about the werewolf?] The pieces still didn't fit. The tracks in the forest—they had seen clear lupine prints. The cow that had been devoured—properly devoured with the bones and teeth left behind. That was not Mrs. Palter's doing, was it?
Hal's contemplations caused her to miss a swift, dodging movement from Mrs. Palter that she would have easily countered had she been entirely focused on the brawl at hand. Mrs. Palter moved more swiftly than she should have been able to, and before Hal could compensate for her lapsed attention, Mrs. Palter dove out of her reach and in one motion tackled and stabbed her husband through the chest.
Hal and Alena were on her before she could pull the knife out to stab again, but the damage was already done. The fading gurgling from the good cathar confirmed it.
It was nearly impossible to hold Mrs. Palter to the ground. So powerful were each of her movements, fueled by her demonic contract, that it took the two of them to hold back just one arm. But Hal and Alena were well-practiced; it was much like grappling a moldgraf monstrosity, and now Hal had turned all of her attention to the physical battle. Though Mrs. Palter fought with all her might to stand, all she was able to succeed in doing was to lift her head. As she did, her hood fell off. For the first time since they had met her in the woods, Hal and Alena looked upon Mrs. Palter's face. So disfigured was it by the power of the demon that had coursed through her time and again, so appalling was the molted flesh, that Hal cried out. Mrs. Palter smiled. Then she began to chant, and as she did, her irises changed from pale blue to dark, glistening black. The black spread quickly to fill the entirety of her eyes. Hal looked to Alena, who was struggling as much as she just to hold Mrs. Palter down. There was nothing they could do when the woman called upon the enormous amount of demonic power she had summoned and threw them off her.
Hal shot through the air until her side smacked into the thick trunk of a tree. Pain radiated out from her shoulder and the side of her head as she collapsed to the ground.
She struggled to get up, to force her limbs to move the way she wanted them to, to compel her vision to focus from three panels to one. The pain in the side of her head was like a blade that was rammed through the whole of her body, pushing her down. But she could not let it, she would not, for she could see there before her, Alena, falling to one blow after another from Mrs. Palter's thrashing fists. Though Alena jumped up every time, she was no match for the well of strength that seemed to be endlessly flowing through the cursed woman. And then Mrs. Palter reached for her blade.
"No." Hal's cry, though fed by her desperation, barely made a sound. She fought against the weakness in her limbs, pushing herself to her feet. But she was not fast enough. Mrs. Palter's blade came down.
Hal's strangled scream was never heard because it was overwhelmed by the sound of a lycanthrope's snarl. Mrs. Palter's blade was stopped, and the woman was thrown to the ground by the single swipe of a wolf's forelimb. Her blood flew everywhere, whipping off the teeth and claws of the giant beast.
Alena rolled away from the fray, and Hal was at her side in an instant. Together they plunged their blades into Mrs. Palter's raging, bloody form.
As the demonic curse drained from the woman's lifeless limbs, her body deflated, and wilted to the ground at their feet. This left Hal and Alena standing shoulder to shoulder, face to face with a massive, panting lycanthrope.
Before they could act, before they could even communicate their intentions to each other, there was a snarl from the trees to their left. And then one from their right. One behind, two in front. Then all around them they saw glowing yellow eyes, reflecting and tarnishing the light of the silver moon. They were surrounded. How many were there? A dozen, perhaps two.
#figure(image("001_Under the Silver Moon/10.jpg", width: 100%), caption: [Art by <NAME>], supplement: none, numbering: none)
Hal felt Alena tense. This was not Alena's usual firm, grounding stance; the girl was rigid, strained. Hal raised her bloodied dagger, locking eyes with the biggest of the lycanthropes, the one standing before them. If they were to die here tonight, it would not be without a fight.
But even as she prepared to strike, the lycanthrope changed its form. It happened so quickly that Hal barely registered it. Suddenly the beast was a human woman, one with hard lines and a striking figure. The silver moon shone off the woman's pale skin and glistened off the white tips of her long hair. Never before had Hal seen a lycanthrope turn back to human form in the heat of battle. Never. It was impossible. Yet here it had happened.
For a moment none of the three of them moved. Then Hal held up her dagger and very slowly, keeping eye contract with the woman, set it on the ground. Alena shifted and cast a questioning look at Hal, but registering Hal's certainty, she proceeded to do the same.
Hal thought she saw a very slight nod from the naked woman before them, and then the woman turned to the rest of the surrounding pack, all of them breathing heavy, battle ready, hungry. The woman shook her head once, short and sharp. A whimper sounded in response, just one, and then the pack turned and disappeared into the trees of the Ulvenwald.
Hal and Alena were left alone with the woman who had just saved their lives.
Hal cleared her throat. She was going to say thank you, but the words would not come. Instead, she unbuttoned her outer coat and offered it to the woman.
"Thank you." The woman took Hal's coat, shouldering it on.
"Thank #emph[you] ," Hal said, finding her voice.
"I did not do it for you. I have been tracking her." She nodded to Mrs. Palter. "And others like her. There are too many in our towns."
"So it was your tracks," Alena said. "And you who ate the cow."
The woman ignored Alena. "If it was not for my desire to end her wretched life, I would not have saved your lives."
Hal started at that assertion.
"But seeing as you have been left alive," the woman went on, "I will tell you this only once: you must cease your killing of my pack."
"The werewolves?" Alena asked.
"If you do not, I will be forced to move against you. And when I do, I will end you." The way the woman said it wasn't as a threat, but as a statement of fact.
Hal bristled. "This is our woods. The Ulvenwald is under our protection."
"We cannot allow werewolves in our domain," Alena added.
"It is not up to you," the woman said. "And it is foolish of you to think that just the two of you could keep this woods safe from what is coming, foolish to think you can even stay alive here yourselves. Leave the woods, little hunters. Leave the woods to us."
"We would never." Alena clenched her hands into fists.
"What is coming?" Hal asked, serious.
"I don't know."
Alena snorted, but Hal was not distracted. There was something about this woman that made Hal heed her words.
"I don't know #emph[exactly] ," the woman said. "But," she indicated the altar and Mrs. Palter, "I have seen enough, and so have you, to know that whatever is out there is worse than werewolves. This world will need us soon. It will welcome the sound of our howl, the muscle of our pack. We may be the only force that can stand against whatever it is that is threatening it."
"We will stand against whatever threatens the Ulvenwald," Alena said. "There is nothing we won't face."
The woman sighed. "If you stay here, you will face your deaths." She dropped Hal's outer coat from her shoulders. "You did not perish tonight only because I intervened, only because of a werewolf. Consider that. Or don't. It is up to you. But know that I am advising you to leave. Get out of the Ulvenwald, and when you do, stay out. And pray, if that is something you do."
"We will not—" Alena began, but the woman had already slipped back into her wolf form. Her transformation was nothing like the usual brutal, bulging transformations that Hal had witnessed in other lycanthropes. This woman was not a usual werewolf. With a final snarl, she turned away from them and glided off into the trees.
Hal and Alena were left standing in the filtered moonlight deep in the dark woods. Once more, the crawling sensation returned to Hal, fingers running up her spine. She could not help her body from shuddering. The feeling was not because of the lycanthrope, it was because of something else entirely—something Hal did not yet know or understand.
Alena looked to her, daring in her eyes, poised to run, but Hal was unsure of which way they should go.
#v(0.35em)
#line(length: 100%, stroke: rgb(90%, 90%, 90%))
#v(0.35em)
<NAME> darted between the tangled trees. The foolish humans. How could they be so blind? She hoped she would not be forced to kill them one day. They were strong and wild. Characteristics she valued. In another life she might have befriended them. But this was not that life; in this life, Arlinn could not have friends.
#figure(image("001_Under the Silver Moon/11.jpg", width: 100%), caption: [Art by <NAME>], supplement: none, numbering: none)
|
|
https://github.com/agrotux/typefaces | https://raw.githubusercontent.com/agrotux/typefaces/main/typefaces_2024-09-01.typ | typst | #set page(numbering: "1", number-align: center)
#show math.equation: set text(weight: 400)
#set heading(numbering: "1.1")
#set page(numbering: "1", number-align: right)
#set text(font: "Lato", fill: black, lang: "sv")
= Typefaces - meaningful characters
#set par(justify: false)
#show: columns.with(1, gutter: 1.3em)
all fonts displayed in 10pt, "regular"
== Serif
#set text(
font: "Alegreya",
size: 10pt
)
=== Alegreya
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Baar Sophia",
size: 10pt
)
=== Baar Sophia
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Bitstream Vera Serif",
size: 10pt
)
=== Bitstream Vera Serif
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Cardo",
size: 10pt
)
=== Cardo
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Crimson Pro",
size: 10pt
)
=== Crimson Pro
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "DejaVu Serif",
size: 10pt
)
=== DejaVu Serif
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Fanwood Text",
size: 10pt
)
=== Fanwood Text
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "FreeSerif",
size: 10pt
)
=== FreeSerif
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Garamond",
size: 10pt
)
=== Garamond
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "EB Garamond",
size: 10pt
)
=== EB Garamond
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Georgia",
size: 10pt
)
=== Georgia
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "IBM Plex Serif",
size: 10pt
)
=== IBM Plex Serif
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Jomolhari",
size: 10pt
)
=== Jomolhari
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Liberation Serif",
size: 10pt
)
=== Liberation Serif
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Libre Baskerville",
size: 10pt
)
=== Libre Baskerville
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Linux Libertine",
size: 10pt
)
=== Linux Libertine
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Lora",
size: 10pt
)
=== Lora
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Merriweather",
size: 10pt
)
=== Merriweather
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Neuton",
size: 10pt
)
=== Neuton
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "New Computer Modern",
size: 10pt
)
=== New Computer Modern
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Nimbus Roman",
size: 10pt
)
=== Nimbus Roman
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "noto serif",
size: 10pt
)
=== Noto Serif
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "PT Serif",
size: 10pt
)
=== PT Serif
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Source Serif Pro",
size: 10pt
)
=== Source Serif Pro
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Reforma 1918",
size: 10pt
)
=== Reforma 1918
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "TeX Gyre Bonum",
size: 10pt
)
=== Tex Gyre Bonum
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "TeX Gyre Pagella",
size: 10pt
)
=== Tex Gyre Pagella
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "TeX Gyre Schola",
size: 10pt
)
=== TeX Gyre Schola
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "TeX Gyre Termes",
size: 10pt
)
=== Tex Gyre Termes
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Times New Roman",
size: 10pt
)
=== Times New Roman
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#colbreak()
#set text(
font: "Lato",
size: 10pt
)
== Sans Serif
#set text(
font: "Alegreya Sans",
size: 10pt
)
=== Alegreya Sans
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Arial",
size: 10pt
)
=== Arial
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Arimo",
size: 10pt
)
=== Arimo
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Baar Metanoia",
size: 10pt
)
=== Baar Metanoia
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Baar Philos",
size: 10pt
)
=== Baar Philos
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Bitstream Vera Sans",
size: 10pt
)
=== Bitstream Vera Sans
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Calibri",
size: 10pt
)
=== Calibri
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "DejaVu Sans",
size: 10pt
)
=== DejaVu Sans
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Fira Sans",
size: 10pt
)
#set text(
font: "Electron",
size: 10pt
)
=== Electron
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
=== Fira Sans
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "FreeSans",
size: 10pt
)
=== FreeSans
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "FreeUniversal",
size: 10pt
)
=== FreeUniversal
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "IBM Plex Sans",
size: 10pt
)
=== IBM Plex Sans
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Inter",
size: 10pt
)
=== Inter
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Lato",
size: 10pt
)
=== Lato
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Liberation Sans",
size: 10pt
)
=== Liberation Sans
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Linux Biolinum",
size: 10pt
)
=== Linux Biolinum
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Manrope",
size: 10pt
)
=== Manrope
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Montserrat",
size: 10pt
)
=== Montserrat
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Nimbus Sans",
size: 10pt
)
=== Nimbus Sans
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Noto Sans",
size: 10pt
)
=== Noto Sans
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Open Sans",
size: 10pt
)
=== Open Sans
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Oswald",
size: 10pt
)
=== Oswald
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "PT Sans",
size: 10pt
)
=== PT Sans
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Reforma 1918",
size: 10pt
)
=== Reforma 1918
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Reforma 1969",
size: 10pt
)
=== Reforma 1969
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Reforma 2018",
size: 10pt
)
=== Reforma 2018
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Roboto",
size: 10pt
)
=== Roboto
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Source Sans Pro",
size: 10pt
)
=== Source Sans Pro
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "TeX Gyre Heros",
size: 10pt
)
=== Tex Gyre Heros
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "TeX Gyre Adventor",
size: 10pt
)
=== Tex Gyre Adventor
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Ubuntu",
size: 10pt
)
=== Ubuntu
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Universalis ADF Std",
size: 10pt
)
=== Universalis ADF Std
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Verdana",
size: 10pt
)
=== Verdana
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Work Sans",
size: 10pt
)
=== Work Sans
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#colbreak()
#set text(
font: "Lato",
size: 10pt
)
== Mono
#set text(
font: "Bitstream Vera Sans Mono",
size: 10pt
)
=== Bitstream Vera Sans Mono
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "CamingoCode",
size: 10pt
)
=== CamingoCode
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Cascadia Code",
size: 10pt
)
=== Cascadia Code
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Cascadia Mono",
size: 10pt
)
=== Cascadia Mono
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Consolas",
size: 10pt
)
=== Consolas
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "DejaVu Sans Mono",
size: 10pt
)
=== DejaVu Sans Mono
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Fira Code",
size: 10pt
)
=== Fira Code
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Fira Mono",
size: 10pt
)
=== Fira Mono
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Hack",
size: 10pt
)
=== Hack
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "IBM Plex Mono",
size: 10pt
)
=== IBM Plex Mono
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Inconsolata",
size: 10pt
)
=== Inconsolata
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Iosevka",
size: 10pt
)
=== Iosevka
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "JetBrains Mono",
size: 10pt
)
=== JetBrains Mono
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Liberation Mono",
size: 10pt
)
=== Liberation Mono
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Monaco",
size: 10pt
)
=== Monaco
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Nimbus Mono PS",
size: 10pt
)
=== Nimbus Mono Ps
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Noto Mono",
size: 10pt
)
=== Noto Mono
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Office Code Pro D",
size: 10pt
)
=== Office Code Pro D
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "PT Mono",
size: 10pt
)
=== PT Mono
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Source Code Pro",
size: 10pt
)
=== Source Code Pro
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "TeX Gyre Cursor",
size: 10pt
)
=== TeX Gyre Cursor
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#set text(
font: "Ubuntu Mono",
size: 10pt
)
=== Ubuntu Mono
"Livet är 120% erfarenhet; varje øyeblikk är unikt!" Life costs \$34 (\£56/78\€) - but {creating beauty} is priceless. Wie können wir das erreichen? Utilisez \[\@\] et \[\$\] pour réussir. Temperaturen i år är < = > 90°C \| ¿Cómo te sientes?
#colbreak()
#set text(
font: "Lato",
size: 10pt
)
= Typefaces - justified columns - meaningful sentences
still 10pt, "regular"
#set par(justify: true)
#show: columns.with(2, gutter: 1.3em)
== Serif
#set text(
font: "Alegreya",
size: 10pt
)
=== Alegreya
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Baar Sophia",
size: 10pt
)
=== Baar Sophia
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Bitstream Vera Serif",
size: 10pt
)
=== Bitstream Vera Serif
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Cardo",
size: 10pt
)
=== Cardo
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Crimson Pro",
size: 10pt
)
=== Crimson Pro
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "DejaVu Serif",
size: 10pt
)
=== DejaVu Serif
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Fanwood Text",
size: 10pt
)
=== Fanwood Text
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "FreeSerif",
size: 10pt
)
=== FreeSerif
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Garamond",
size: 10pt
)
=== Garamond
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "EB Garamond",
size: 10pt
)
=== EB Garamond
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Georgia",
size: 10pt
)
=== Georgia
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "IBM Plex Serif",
size: 10pt
)
=== IBM Plex Serif
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Jomolhari",
size: 10pt
)
=== Jomolhari
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Liberation Serif",
size: 10pt
)
=== Liberation Serif
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Libre Baskerville",
size: 10pt
)
=== Libre Baskerville
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Linux Libertine",
size: 10pt
)
=== Linux Libertine
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Lora",
size: 10pt
)
=== Lora
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Merriweather",
size: 10pt
)
=== Merriweather
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Neuton",
size: 10pt
)
=== Neuton
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "New Computer Modern",
size: 10pt
)
=== New Computer Modern
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Nimbus Roman",
size: 10pt
)
=== Nimbus Roman
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "noto serif",
size: 10pt
)
=== Noto Serif
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "PT Serif",
size: 10pt
)
=== PT Serif
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Source Serif Pro",
size: 10pt
)
=== Source Serif Pro
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Reforma 1918",
size: 10pt
)
=== Reforma 1918
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "TeX Gyre Bonum",
size: 10pt
)
=== Tex Gyre Bonum
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "TeX Gyre Pagella",
size: 10pt
)
=== Tex Gyre Pagella
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "TeX G<NAME>",
size: 10pt
)
=== TeX G<NAME>ola
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "TeX <NAME>",
size: 10pt
)
=== Tex G<NAME>
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Times New Roman",
size: 10pt
)
=== Times New Roman
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#colbreak()
#set text(
font: "Lato",
size: 10pt
)
== Sans Serif
#set text(
font: "Alegreya Sans",
size: 10pt
)
=== Alegreya Sans
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Arial",
size: 10pt
)
=== Arial
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Arimo",
size: 10pt
)
=== Arimo
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Baar Metanoia",
size: 10pt
)
=== Baar Metanoia
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Baar Philos",
size: 10pt
)
=== Baar Philos
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Bitstream Vera Sans",
size: 10pt
)
=== Bitstream Vera Sans
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Calibri",
size: 10pt
)
=== Calibri
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "DejaVu Sans",
size: 10pt
)
=== DejaVu Sans
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Fira Sans",
size: 10pt
)
#set text(
font: "Electron",
size: 10pt
)
=== Electron
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
=== Fira Sans
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "FreeSans",
size: 10pt
)
=== FreeSans
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "FreeUniversal",
size: 10pt
)
=== FreeUniversal
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "IBM Plex Sans",
size: 10pt
)
=== IBM Plex Sans
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Inter",
size: 10pt
)
=== Inter
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Lato",
size: 10pt
)
=== Lato
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Liberation Sans",
size: 10pt
)
=== Liberation Sans
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Linux Biolinum",
size: 10pt
)
=== Linux Biolinum
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Manrope",
size: 10pt
)
=== Manrope
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Montserrat",
size: 10pt
)
=== Montserrat
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Nimbus Sans",
size: 10pt
)
=== Nimbus Sans
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Noto Sans",
size: 10pt
)
=== Noto Sans
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Open Sans",
size: 10pt
)
=== Open Sans
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Oswald",
size: 10pt
)
=== Oswald
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "PT Sans",
size: 10pt
)
=== PT Sans
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Reforma 1918",
size: 10pt
)
=== Reforma 1918
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Reforma 1969",
size: 10pt
)
=== Reforma 1969
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Reforma 2018",
size: 10pt
)
=== Reforma 2018
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Roboto",
size: 10pt
)
=== Roboto
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Source Sans Pro",
size: 10pt
)
=== Source Sans Pro
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "TeX Gyre Heros",
size: 10pt
)
=== Tex Gyre Heros
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "TeX Gyre Adventor",
size: 10pt
)
=== Tex Gyre Adventor
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? <NAME>agt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Ubuntu",
size: 10pt
)
=== Ubuntu
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Universalis ADF Std",
size: 10pt
)
=== Universalis ADF Std
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Verdana",
size: 10pt
)
=== Verdana
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Work Sans",
size: 10pt
)
=== Work Sans
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#colbreak()
#colbreak()
#set text(
font: "Lato",
size: 10pt
)
== Mono
#set text(
font: "Bitstream Vera Sans Mono",
size: 10pt
)
=== Bitstream Vera Sans Mono
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "CamingoCode",
size: 10pt
)
=== CamingoCode
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Cascadia Code",
size: 10pt
)
=== Cascadia Code
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Cascadia Mono",
size: 10pt
)
=== Cascadia Mono
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Consolas",
size: 10pt
)
=== Consolas
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "DejaVu Sans Mono",
size: 10pt
)
=== DejaVu Sans Mono
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Fira Code",
size: 10pt
)
=== Fira Code
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Fira Mono",
size: 10pt
)
=== Fira Mono
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Hack",
size: 10pt
)
=== Hack
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "IBM Plex Mono",
size: 10pt
)
=== IBM Plex Mono
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Inconsolata",
size: 10pt
)
=== Inconsolata
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Iosevka",
size: 10pt
)
=== Iosevka
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "JetBrains Mono",
size: 10pt
)
=== JetBrains Mono
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Liberation Mono",
size: 10pt
)
=== Liberation Mono
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Monaco",
size: 10pt
)
=== Monaco
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Nimbus Mono PS",
size: 10pt
)
=== Nimbus Mono Ps
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Noto Mono",
size: 10pt
)
=== Noto Mono
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Office Code Pro D",
size: 10pt
)
=== Office Code Pro D
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "PT Mono",
size: 10pt
)
=== PT Mono
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Source Code Pro",
size: 10pt
)
=== Source Code Pro
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "TeX Gyre Cursor",
size: 10pt
)
=== TeX Gyre Cursor
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
#set text(
font: "Ubuntu Mono",
size: 10pt
)
=== Ubuntu Mono
Yxskaftbud, ge vår WC-zonmö IQ-hjälp! The quick brown fox jumps over a lazy dog. Vår sære Zulu fra badeøya spilte jo whist og quickstep? Victor jagt zwölf Boxkämpfer quer über den großen Sylter Deich; el veloz murciélago hindú comía feliz cardillo y kiwi.Voyez le bon whisky que je garde près de l'âtre.
|
|
https://github.com/maucejo/presentation_polylux | https://raw.githubusercontent.com/maucejo/presentation_polylux/main/README.md | markdown | MIT License | # Modèle Typst pour les présentation Cnam
[]()
[](https://github.com/maucejo/elsearticle/blob/main/LICENSE)
[](https://github.com/maucejo/elsearticle/blob/main/docs/manual.pdf)
Ce dépôt contient un modèle en langage Typst pour les présentation du Cnam.
## Usage
Pour utiliser le modèle, il faut l'importer dans votre fichier principal `typ` en utilisant la commande suivante :
```typ
#import "path to template/pres-template.typ": *
```
Pour plus d'informations, veuillez consulter le [manuel](https://github.com/maucejo/Cnam_presentation_template/blob/main/docs/manual.pdf).
|
https://github.com/mismorgano/UG-FunctionalAnalyisis-24 | https://raw.githubusercontent.com/mismorgano/UG-FunctionalAnalyisis-24/main/tareas/Tarea-01/Tarea-01.typ | typst | #import "../../config.typ": config, exercise, proof
#show: doc => config([Tarea 1], doc)
#let cls(S) = $overline(#S)$
#exercise[1.2][
Sea $X$ un espacio lineal normado. Supongamos que para $x, y in X$ tenemos que
$norm(x+y) = norm(x) + norm(y)$. Muestra que $norm(alpha x + beta y) = alpha norm(x) + beta norm(y)$ para
todo $alpha, beta >= 0$.]
*Demostración:*
Sean $alpha, beta >= 0$, sin perdida de generailad supongamos que $alpha>= beta$, así
$alpha - beta >=0$. Notemos que
$ alpha x + beta y = alpha x + alpha y - alpha y + beta y = alpha(x+y) - (alpha - beta) y, $
por lo cual
$ norm(alpha x + beta y) &= norm(alpha(x+y) - (alpha - beta) y) \
&>= abs(alpha)norm(x+y) - abs(alpha-beta)norm(y) \
&= alpha norm(x+y) - (alpha -beta)norm(y) \
&= alpha (norm(x) + norm(y)) - (alpha -beta)norm(y)\
&= alpha norm(x) + beta norm(y). $
Por otro lado sabemos que
$ norm(alpha x + beta y) <= norm(alpha x) + norm( beta y) = abs(alpha) norm(x) + abs(beta) norm(y) = alpha norm(x) + beta norm(y), $
pues $alpha, beta >=0$. De lo anterior obtenemos lo deseado.
// Notemos que $alpha x, beta y in X$, luego por hipotesis se cumple que
// $ norm(alpha x + beta y) &= norm(alpha x) + norm(beta y) = abs(alpha)norm(x) + abs(beta)norm(y)\
// &= alpha norm(x) + beta norm(y), $
// pues $alpha, beta >= 0$.
#h(1fr) $square$
#exercise[1.3][Muestra que $overline("span")(L) = overline("span"(L))$ y $overline("conv")(M) = overline("conv"(M))$]
*Demostración:*
Primero mostraremos que la cerradura de un subespacio (lineal) es un subespacio lineal.
Supongamos $S$ es un subespacio lineal, sean $x, y in cls(S)$, entonces existen sucesiones ${x_n}, {y_n} subset S$ tales
que $ lim_(n -> infinity) x_n = x, quad lim_(n -> infinity) y_n = y, $
dado que $S$ es lineal tenemos que $x_n + y_n in S$ para todo $n in NN$ y además
$ lim_(n -> infinity) (x_n + y_n) = lim_(n -> infinity) x_n + lim_(n -> infinity) y_n = x +y, $
por lo cual $x+y in cls(S)$.
De manera similar, dado $alpha in bb(K)$ tenemos que $alpha x_n in S$ para todo $n in NN$ y como $ lim_(n -> inf) alpha x_n = alpha x, $
entonces $alpha x in cls(S)$. Por lo anterior obtenemos que $cls(S)$ es un subespacio lineal.
Regresando con la demostración,
notemos que $overline("span"(L))$ es un subespacio cerrado que contiene a $L$, luego $ cls("span")(L) subset cls("span"(L)) $, más aún
tenemos que $cls("span")(L)$ es cerrado, pues es intersección de cerrados, que contiene a $L$ por lo cual $cls("span"(L)) subset cls("span")(L)$
#h(1fr) $square$
#exercise[1.4][Muestra que $C$ es un conjunto convexo es un espacio vectorial si y solo si
$sum lambda_i x_i in C$ siempre que $x_1, dots, x_n in C$ y $lambda_1, dots, lambda_n >= 0$ cumplen $sum lambda_i = 1$.]
#proof[Supongamos primero que $C$ es un conjunto convexo en un e.v, procedamos por inducción sobre $n$.
Para $n=2$, el resltado se sigue por la definición de convexidad. Supongamos ahora que el resultado es valido para $n=k$ y
veamos que se cumple para $n=k+1$ .
Sean $x_1, dots, x_(k+1) in C$ y $lambda_1, dots, lambda_(k+1) >= 0$. Si $sum_(i=1)^(k) lambda_i = 0$ entonces $lambda_i = 0$ para $i=1, dots, k$
y $lambda_(k+1)=1$ luego
$ sum_(i=1)^(k+1) lambda_i x_i = x_(k+1) $
el cual esta en $C$.
Ahora, si $sum_(i=1)^(k) lambda_i >0$ tenemos que
$ sum_(i=1)^(k+1) lambda_i x_i &= (sum_(i=1)^(k) lambda_i x_i) + lambda_(k+1) x_(k+1) \
&= sum_(i=1)^(k) lambda_i (sum_(i=1)^(k) lambda_i/(sum_(i=1)^(k) lambda_i) x_i) + lambda_(k+1) x_(k+1), $
notemos que $lambda_i/(sum_(i=1)^(k) lambda_i) >= 0$ pue $lambda_i>=0$ y además $sum_(i=1)^(k) lambda_i/(sum_(i=1)^(k) = 1$, luego,
por hipotesis de inducción se cumple que $sum_(i=1)^(k) lambda_i/(sum_(i=1)^(k) lambda_i) x_i in C$.
Dado que $(sum_(i=1)^(k) lambda_i) + lambda_(k+1) =1$ y $C$ es convexo tenemos que
$ sum_(i=1)^(k) lambda_i (sum_(i=1)^(k) lambda_i/(sum_(i=1)^(k) lambda_i) x_i) + lambda_(k+1) x_(k+1) in C, $
es decir,
$ sum_(i=1)^(k+1) lambda_i x_i in C, $
como queremos.
Por el principio de inducción se cumple el resultado.
Supongamos ahora que $sum lambda_i x_i in C$ siempre que $x_1, dots, x_n in C$ y $lambda_1, dots, lambda_n >= 0$ cumplen $sum lambda_i = 1$
Dados $x, y in C$ consideramos $lambda_1 = t$ y $lambda_2 = 1-t$, con $t in [0, 1]$ en lo anterior, que es justamente la definición de que $C$ sea convexo.]
#exercise[1.5][Sean $A$ y $B$ dos conjuntos convexos es un espacio normado $X$.
Muestra que $"conv"(A union B) = {lambda x + (1-lambda) y: x in A, y in B, lambda in [0, 1]}$.]
*Demostración:*
Sea $ C={lambda x + (1-lambda) y: x in A, y in B, lambda in [0, 1]}. $
Primero veamos que $C$ es convexo, sea $x, y in C$, entonces existen $a_1, a_2 in A$, $b_1, b_2 in B$ y $t_1, t_2 in [0, 1]$ tales que
$ x = a_1 t_1 + (1-t_1) b_1, quad y = a_2 t_2 + (1-t_2)b_2. $
Dado $t in [0,1]$ se cumple que
$ t x + (1-t)y &= t(a_1 t_1 + (1-t_1) b_1) + (1-t)(a_2 t_2 + (1-t_2)b_2) \
&= t t_1 a_1 + t (1-t_1) b_1 + (1-t)t_2 a_2 + (1-t)(1-t_2)b_2\
&= t t_1 a_1 + (1-t)t_2 a_2 + t (1-t_1) b_1 + (1-t)(1-t_2)b_2, $
veamos que $ t t_1 a_1 + (1-t)t_2 a_2 = (t t_1 + (1-t)t_2 ) ( (t t_1)/(t t_1 + (1-t)t_2 ) a_1 + ((1-t)t_2)/(t t_1 + (1-t)t_2 ) a_2 ) $
notemos que $t t_1 + $
#h(1fr) $square.filled$
#exercise[1.8][Sea $1 <= p <= q <= infinity$. Muestra que $norm(x)_(l_q) <= norm(x)_(l_p)$ para $x in l_p$ y
$norm(f)_(L_p) <= norm(f)_(L_q)$ para $f in L_q[0, 1]$.]
#exercise[1.9][Sea $f in L_(p_0)[0, 1]$ para algún $p_0>1$. Muestra que $lim$]
#proof[] |
|
https://github.com/Hobr/njust_thesis_typst_template | https://raw.githubusercontent.com/Hobr/njust_thesis_typst_template/main/page/reference.typ | typst | MIT License | // 字体
#import "../util/font.typ": fonts, fontSize
#let showReference(ref) = text(
lang: "en",
font: (fonts.en, fonts.zh_宋体),
size: fontSize.五号,
)[#bibliography(
"../template/" + ref,
title: text(
font: (fonts.en, fonts.zh_宋体),
size: fontSize.四号,
)[参考文献],
)]
|
https://github.com/sitandr/typst-examples-book | https://raw.githubusercontent.com/sitandr/typst-examples-book/main/src/packages/wrapping.md | markdown | MIT License | # Wrapping figures
The better native support for wrapping is planned, however, something is already possible via package:
```typ
#import "@preview/wrap-it:0.1.0": wrap-content, wrap-top-bottom
#set par(justify: true)
#let fig = figure(
rect(fill: teal, radius: 0.5em, width: 8em),
caption: [A figure],
)
#let body = lorem(40)
#wrap-content(fig, body)
#wrap-content(
fig,
body,
align: bottom + right,
column-gutter: 2em
)
#let boxed = box(fig, inset: 0.5em)
#wrap-content(boxed)[
#lorem(40)
]
#let fig2 = figure(
rect(fill: lime, radius: 0.5em),
caption: [Another figure],
)
#wrap-top-bottom(boxed, fig2, lorem(60))
```
<div class="warning">Limitations: non-ideal spacing near warping, only top-bottom left/right are supported.</div> |
https://github.com/voXrey/cours-informatique | https://raw.githubusercontent.com/voXrey/cours-informatique/main/typst/19-bruteforce-backtracking.typ | typst | #import "@preview/codly:0.2.1": *
#show: codly-init.with()
#codly()
#set text(font: "Roboto Serif")
= Brute Force & Backtracking <brute-force-backtracking>
La solution brute force à un problème de recherche / optimisation consiste à tout tester :
```python
S:list # liste finie de solutions
# Problème de recherche
for s in S:
if is_solution(s):
return True
return False
# Problème d'optimisation
opt:int # = +infini ou -infini
for s in S:
if is_better(score(s), opt): # si s est mieux que l'ancien mieux
opt = score(s)
return opt
```
La difficulté est d'énumérer les éléments de S. C'est l'espace de recherche (space search). Cela revient à construire une bijection entre S et $lr([0 , \# S - 1])$
== I - Structures ensemblistes usuelles et énumération <i---structures-ensemblistes-usuelles-et-énumération>
On en dénombre 4 classiques :
- Intervalle de $NN$
- Produit cartésien
- Sous-ensemble d'un ensemble fini E
- Permutations
Mais il en existe également des moins classiques, il faudra s'adapter.
On reprend les exemples du chapitre 17.
==== 1. Recherche d'un nombre premier dans \[a,b\] <recherche-dun-nombre-premier-dans-ab>
$-->$ Énumérer l'intervalle $\[a,b\] subset.eq NN$
$-->$ ```ml for i = a to b do ...```
Remarque : S'il y a solution, le plus petit est trouvé d'abord, donc on résout aussi le problème d'optimisation associé.
==== <section>
==== 2. Somme d'une tranche d'un tableau <somme-dune-tranche-dun-tableau>
Soit a un tableau d'entiers et $s = l e n lr((a))$
On cherche $lr((i , j)) in lr([0 , n - 1]) times lr([1 , n])$ avec $i < j$
$-->$ Produit cartésien
$-->$ De manière générale, pour énumérer $A times B$ on effectue une double boucle telle que celle-ci :
```python
for a in A:
bar()
...
for b in B:
foo()
...
```
==== 3. Subset Sum | sac à dos <subset-sum-sac-à-dos>
$-->$ Énumérer les sous-ensembles $F subset.eq E$
Solution classique :
Généralement E est représenté par un tableau de longueur $n = \# E$
On encode alors un sous-ensemble F par un tableau $T_F$ de booléens de longueur n tel que $forall i in lr([0 , n - 1]) : T_F lr([i]) = T r u e arrow.l.r.double i in F$
Comment énumérer les $T_F$ ?
$-->$ Par ordre lexico-graphique, ce qui correspond par ailleurs à énumérer les entiers de 0 à $2^n - 1$ en binaire.
==== 4. Les N-dames <les-n-dames>
Nouvelle difficulté : identifier S
Une première idée : On cherche à placer N dames sur $N ²$ cases.
$-->$ On numérote les cases de 0 à $N^2 - 1$. Un candidat est alors une façon de choisir N cases parmi les $N^2$.
$arrow.r.double$ Il y a $binom(N^2, N)$ candidats, ce est égal à : $frac(N^2 !, N ! lr((N^2 - N)) !)$
Une meilleure idée :
- Il y aura exactement 1 dame par colonne donc on appelle dame $n degree i$ celle qui sera placée dans la colonne $i$.
- Un candidat est alors une fonction $f : lr([0 , N - 1]) arrow.r lr([0 , N - 1])$ et qui indique "la dame $n degree i$ est sur la ligne $n degree f lr((i))$".
- De plus f est injective puisqu'on ne peut pas avoir 2 dames sur la même ligne.
- Donc elle est bijective par cardinal.
$arrow.r.double$ f est une permutation
Comment les énumérer ? Avec l'ordre lexico-graphique.
==== 5. Problème du Cavalier <problème-du-cavalier>
Solution naïve : Les candidats sont des suites de cases, $f : lr([0 , N^2 - 1]) arrow.r lr([0 , N^2 - 1])$ et f est une permutation $arrow.r.double N ² !$ candidats !
Bonne solution : Le cavalier a 8 déplacements possibles à chaque étape et il y en a $N^2$.
Une course de cavalier se décrit par une suite de $N^2 - 1$ déplacements parmi ${ A , B , C , D , E , F , G , H }$.
$arrow.r.double { A , B , C , D , E , F , G , H }^(N^2 - 1)$
$arrow.r.double 8^(N^2 - 1)$ candidats.
#figure(
align(
center,
)[#table(
columns: 5,
align: (col, row) => (center, center, center, center, center,).at(col),
inset: 6pt,
[],
[A],
[],
[B],
[],
[H],
[],
[],
[],
[C],
[],
[],
[C],
[],
[],
[G],
[],
[],
[],
[D],
[],
[F],
[],
[E],
[],
)],
)
== II - BackTracking (retour sur trace) <ii---backtracking-retour-sur-trace>
On s'intéresse dans un premier temps aux problèmes de recherche. L'idée du backtracking est d'organiser l'espace de recherche S sous forme d'un arbre afin que les feuilles de l'arbre correspondent de manière bijective aux éléments $s in S$.
Les nœuds représentent alors des "candidats partiels" de telle sorte qu'un candidat partiel ait quelque chose en commun avec tous les candidats $s in S$ qui sont ses feuilles dans l'arbre.
Pour énumérer S, on effectue un parcours en profondeur de l'arbre.
==== Illustration sur le cavalier <illustration-sur-le-cavalier>
Dans les nœuds on écrit la position actuelle du cavalier. Chaque nœud a 8 enfants qui correspondent aux sauts possibles A, B,…H.
Dès lors qu'un nœud se situe en dehors de l'échiquier, on arrête de l'explorer, on ne construit pas le sous-arbre de ce nœud (idem si case déjà visitée).
Le backtracking consiste à effectuer le parcours en profondeur de cet arbre sans le construire.
==== Deuxième exemple : Subset Sum <deuxième-exemple-subset-sum>
Il s'agit d'énumérer $P lr((lr([0 , n - 1])))$. Comment organiser S dans un arbre ? Il faut éviter la redondance.
Une bonne idée serait alors de créer un arbre de décision. Dans l'ordre de 0 à n-1, on se pose la question "je prends ou pas ?".
==== Résumé <résumé>
Si la façon de représenter S est pertinente, on peut s'épargner la recherche de certains sous-arbres. Dans le cas des optimisations, on va pouvoir ne pas explorer les sous-arbres qui ne respectent plus la contrainte mais il faudra bien trouver toutes les solutions pour déterminer l'optimum (ouverture sur le Branch and Bound).
|
|
https://github.com/kilpkonn/typst-thesis | https://raw.githubusercontent.com/kilpkonn/typst-thesis/main/abstract.typ | typst | MIT License | #lorem(50)
The thesis is written in English and is #context counter(page).at(<end>).first() pages long,
including #context counter(heading).at(<conclusion>).first() chapters,
#context counter(figure.where(kind: image)).final().first() figures
#context counter(figure.where(kind: raw)).final().first() code listings and
#context counter(figure.where(kind: table)).final().first() tables.
|
https://github.com/polarkac/MTG-Stories | https://raw.githubusercontent.com/polarkac/MTG-Stories/master/stories/042%20-%20Strixhaven%3A%20School%20of%20Mages/003_Episode%202%3A%20Lessons.typ | typst | #import "@local/mtgstory:0.2.0": conf
#show: doc => conf(
"Episode 2: Lessons",
set_name: "Strixhaven: School of Mages",
story_date: datetime(day: 31, month: 03, year: 2021),
author: "<NAME>",
doc
)
Tavver didn't know how long he had waited in that cramped tunnel beneath the Biblioplex—hours, certainly, though it felt like far longer. He didn't feel safe moving during the day; eventually, he'd have to emerge from the underground passage and cross the ravine separating the school from the surrounding woodlands. After that, he'd be in tree-cover, mostly, but even that was no protection against being seen. This was a school full of #emph[mages] —damn it all! The best mages in all of Arcavios, no matter what the other Oriq said about all the undeserving brats. And what if one of the Founders happened to fly overhead? He had no interest in being incinerated by dragonflame. No, Tavver always thought himself a pragmatist. So, very pragmatically, he waited until nightfall.
He wasn't excited about facing Extus again—not after failing his mission. But he would worry about that when he got out alive. Tavver had seen true darkness in that professor's violet eyes. She'd meant to kill him—and for what? So that Extus could have some dusty old book he remembered from however many years ago?
Finally, with night fallen, he could start the hard trek home through the forest and over the rocky bluffs. It would be a long night.
#v(0.35em)
#line(length: 100%, stroke: rgb(90%, 90%, 90%))
#v(0.35em)
Three weeks earlier, before Lukka met the Oriq mages—before they'd kidnapped him, in fact—he squinted against the light, his stomach still churning from planeswalking. Never a pleasant sensation. Across the grassy field ahead of him was a small village. He could see a few people milling about; one woman was waving her hands over a row of tilled earth, muttering a growth spell, while another ordered what looked like a mud construct to drag a plow through the field.
He wandered through unpaved streets until the smell of food drew him into an inn. Ignoring the stares and whispers of the people seated at the squat wooden tables, Lukka sat down at the wooden bar.
"Looking for something, stranger?" said the innkeeper, a round man with a head of robust curls.
"A hot meal," said Lukka. The innkeeper hesitated as though about to say something, then nodded and moved toward the kitchen.
"Haven't seen clothes like that before," came a voice behind Lukka. "You're not from around here, I imagine."
He turned. A tall man in the same rough clothing as the rest of the townsfolk had stood up from his table and was walking over.
"No," said Lukka, turning away. "Guess I'm not."
"You know who they say dress strange and act stranger? Coming through little towns like ours to recruit? The Oriq," said the man behind him. His tone was far from friendly.
"I don't know what you're talking about."
"Maybe. Maybe not. Where are you from, then?"
Lukka kept his eyes straight ahead, not bothering to even look at the loudmouthed man. "You wouldn't know it."
He heard the man suck his teeth. The innkeeper still hadn't returned from the kitchen. Lukka was starting to doubt he ever would.
"Okay, Oriq, I think I've heard enough. We don't take kindly to meddlers in this town, or those who seek to disturb the peace. If we were a proper city, we'd get the closest, least busy Dragonsguard to sort you out. But we're just a small farming village—so we've learned to deal with strangers ourselves."
Lukka felt, rather than saw, the rush of magic as the man began a spell. #emph[Is everyone a damn mage on this plane? ] He turned and, in one fluid motion, smashed his fist into the man's jaw. The man dropped limply, the wispy energy curled around one hand dissipating. Lukka had an instant to breathe before another man crashed through the door of the inn, a ball of flame hovering above one outstretched hand. Lukka got a few steps away before the firebolt splashed against the back of his coat, knocking him through the glass of a nearby window and into the street.
The stink of charred leather filled his nose, mingling with the searing pain across his shoulders. Lukka snarled and cast his senses out over the village, finding every vulnerable mind he could. He called to them, stumbling back to his feet.
The fireball-throwing man had left the inn and was joined outside by two other burly-looking townsfolk. "Where are your friends? We know you Oriq scum like to travel in packs."
"Oh, they'll be coming along any minute now," said Lukka.
The man lifted his hand and began to fill it once again with fire. Before he could finish, a dog leapt through the air, its sharp teeth flashing as they sank into his arm. The man screamed, the flames sputtering out as he fought to free himself. He managed to tear his arm free just as a horse charged at him. He and his companion dove out of the way, but the horse followed them, spurred by Lukka's rage. It reared back, then brought its hooves down hard.
Lukka's smirk faded as hunger shot through his stomach. He staggered down the road, his mind absently following the fight through the beasts, until the noise faded behind him.
#v(0.35em)
#line(length: 100%, stroke: rgb(90%, 90%, 90%))
#v(0.35em)
Usually, reflected Liliana, one did not willingly walk into a dragon's lair—or if one did, they did so with a death wish and some very keen blades. She had neither as she approached the tangled grove where <NAME> made her home. All she brought with her were questions that needed answering.
She pushed aside a low-hanging bough, trying to make as much noise as possible. Sneaking up on a dragon was an even worse idea than visiting one. But the nest was empty, just a broad patch of foliage pressed flat into the earth, and Liliana felt relieved in spite of herself. #emph[<NAME> is gone] . #emph[What am I really shrinking from?]
The lair was surrounded by dark-leaved trees leaning over the divot in the earth like jurors. The scent of decay mingled with fresh earth, but Liliana knew that Beledros had a formidable collection of arcane writings tucked away. Glowing spheres of various sizes lay tucked into massive root structures, protecting their contents from the humid air. Maybe there was something in the books and scrolls that could help her bring Gideon back. Liliana peered into one of the globes, careful not to get stuck in the thick mud underfoot.
She was looking through her fifth sphere when the sound of wings brought her attention to the sky. Liliana took a deep breath and remembered to adjust her professor's uniform as the shadow of <NAME> passed over her.
#figure(image("003_Episode 2: Lessons/01.jpg", width: 100%), caption: [Art by: <NAME>], supplement: none, numbering: none)
Beledros circled the spot twice before landing with an earth-shaking tremor. She folded back her black feathered wings as she studied Liliana with those eerie, bright eyes. "Taiva may be harsh at times, but surely dealing with him is not as troublesome as trekking all the way out here, Professor."
"What I need isn't something the director can help me with."
Beledros gave what Liliana thought was a curious look.
"I found some of your work on aetheric reincorporation." Liliana pulled a pointed piece of metal from her pocket. It was the only piece of Gideon she had, a tip from one of the blades of his sural. "What would it take for such methods to work on humans?"
Beledros made a rumbling noise, the sound vibrating the ground beneath her. "This smells of a dangerous sort of meddling to me. Some questions are better left unanswered."
"I didn't come here for a lecture. I just want a simple answer."
"When it comes to aether, there are no simple answers." Beledros walked past Liliana, making her way into a deeper recess in the side of the crater. She turned and laid down, wrapping her tail around her massive form. "You speak of the very essence of life. It cannot be ordered about like a pet. Resurrection—apart from baser necromancy, you understand—is fiendishly difficult, even for myself."
Liliana set her jaw. "And what about the child of Professor Gladefell?"
The dragon went still, each huge black eye a bottomless pit. "No. That was~something I will not see repeated. For all our sakes."
"I am not some wayward student, Beledros." Liliana stepped toward the dragon, Gideon's blade cold in her hand. "I do not need your coddling, and I do not need your protection."
"Perhaps not," Beledros said. "But it is not you I would be protecting."
"What do you care about humans, anyway? I imagine we seem little more than insects to you. None of the Founders have even been to the university in years."
The dragon turned her head and closed her huge, heavy-lidded eyes. "The deans are more than capable of keeping order and peace. As are the Dragonsguards and the Oracle." She let out a little chuckle, stirring the layer of decaying leaves and mulch underneath them. "Even the Archaics do their part."
Liliana's nails dug into her palm. The dragon had to know more than she was letting on. And this was her last hope. Gideon's last hope. "Please. He took my death. Help me give him back his life."
Beledros cracked an eye open and looked at her for a moment. The wind blew over the top of the crater walls, stirring the dark trees surrounding the lair. Finally, she closed her eye again. "I cannot."
A jolt of pain in Liliana's hand told her she had gripped the piece of the sural a little too tightly. She stared down at her bleeding palm, trying to calm the storm of her emotions. This wasn't a fight she could win with force or sheer will. Liliana tucked the blade piece back into her pocket and turned to leave. She was halfway up the crater when Beledros spoke.
"The pain can be unbearable at times. But in the end, how we honor the dead is reflected in how we treat the living."
Liliana looked back, but the dragon was still curled up in the side of the crater, slowly drifting toward sleep.
#v(0.35em)
#line(length: 100%, stroke: rgb(90%, 90%, 90%))
#v(0.35em)
Lukka stumbled as he moved across a stony ledge, minding his step along the edge of a sheer cliff. Far below, short grass and scrawny trees held on bitterly to life. His hunger had only gotten worse, tightening his stomach more and more with each shaky step. What little food he'd managed to hunt down was long gone, and he'd run out of water hours ago.
#figure(image("003_Episode 2: Lessons/02.jpg", width: 100%), caption: [Art by: <NAME>], supplement: none, numbering: none)
The ledge suddenly gave way beneath him, crumbling into loose stone. Lukka cried out as his ankle twisted. He threw out his hands, reaching for anything to save him from the long fall, and his fingers caught on the edge of a sharp, flat stone. Gritting his teeth, he pulled himself up the side of the cliff, legs scrambling for purchase, and finally threw himself back onto the stone shelf. He laid there for what felt like an eternity, his lungs burning as he sucked in gulps of air.
Thoughts of his near demise faded as his gaze caught on the rock that had saved him. It floated in the air, the end facing him smooth and curved. Lukka stood up, finding more of the odd rocks hovering around the side of the cliff. Together, they formed a half-circle, as if the rest of them were lost within the cliff itself.
A small noise grabbed his attention Lukka tensed, ready for trouble—but, as it came again, it seemed a pitiful sound, soft and weak.
Lukka followed it until he found a pile of stones. He dropped to his knees, pushing one of the stones away. A pair of golden eyes looked back out at him. The creature gave a miserable yelp, blinking against the light. As Lukka shoved the rest of the stones aside, he saw that her gray fur was dirty, covering the spots that ran in a camouflage pattern along her back. A long gash ran across the creature's snout, and something had taken a chunk out of one of her pointed, black-tipped ears.
Free now, the foxlike creature limped past the stones Lukka had moved, putting more space between them. He sat down hard, the strength in his legs finally giving out. He felt faint. "Go on, then. Get."
The fox turned and darted around the curve of the cliff just as consciousness slipped away.
When he woke, the first thing he registered was her presence. He kept still, slowly opening one eye. She sat on her haunches a few paces away, staring at him. Then her eyes flicked to the ground beside him.
Lukka followed her gaze. A pile of berries and nuts lay beside his leg. "Thank you."
The fox tensed, rising to her feet.
Lukka started to raise a hand but stopped himself. He stared at her, the silence stretching as the first sun began to rise in the distance. Finally, Lukka took a deep breath and cast out his bonder's senses.
The warm brush of fur caressed his mind as the link between them settled. It had been a while since he used this gentler magic—not for a servant, but a partner. He hadn't even realized how much he'd missed it.
#figure(image("003_Episode 2: Lessons/03.jpg", width: 100%), caption: [Art by: <NAME>], supplement: none, numbering: none)
#v(0.35em)
#line(length: 100%, stroke: rgb(90%, 90%, 90%))
#v(0.35em)
Liliana pushed off the side of the towering metal torch and continued her trek back to Strixhaven empty-handed. She'd been gone for days by this point—days of classes that had gone untaught, meetings that had gone unattended, professorial duties that had gone undone. After Beledros's refusal to help her, she'd followed rumors of an Archaic to the ruins of Caerdoon. But she'd found no massive, mystical giant packed full of arcane secrets. In fact, she hadn't found much of anything. It had been for nothing—and now she would be questioned by the other professors. Or worse, by <NAME> and Lisette.
An animal screech sounded in the distance. The strangled cry came from somewhere up ahead, off the path, though Liliana couldn't see past the thick canopy of trees. She stepped into the undergrowth, keeping low.
In a clearing not far off the path, seven people stood in a circle. Purple magic flared around their outstretched hands, the same color as the light that wound in smoky trails around their masks. Liliana pressed against the gnarled trunk of an old tree and watched as the band of Oriq agents surrounded a large white stag.
The beast bleated and reared back, swiping at one of the agents with its hooves. One figure fell back, but the others pushed forward, forcing it toward the metal crate that lay open behind it. Inch by inch, the stag backed into the crate, its cries splitting the air—then sharply cut off as the door of the metal box slammed shut.
Liliana watched, silent and still, as they loaded the captured stag onto a wagon waiting nearby. Eventually, the creak of the wagon wheels faded into the distance.
#v(0.35em)
#line(length: 100%, stroke: rgb(90%, 90%, 90%))
#v(0.35em)
In the distance, Lukka could make out the curling tail of smoke from a chimney somewhere beyond the woodland. In another world, another plane, he would have felt relief. Finally, somewhere soft to rest his head. Somewhere to get a decent meal where he wouldn't have to mind-control rabbits into letting him break their necks. But here, in Arcavios, he knew he'd just get treated with the same suspicion as he had been everywhere else. The people of this plane hated everything new, everything they didn't understand. Like those Oriq, the masked mages who used magic "forbidden by the colleges of Strixhaven," whatever that meant. Every villager seemed to think there was an Oriq agent hiding under their bed. In some ways, it reminded him of home, of the way <NAME> had looked at him when Lukka had first shown his bonder magic. This was a place ruled by fear.
The sound of raised voices pulled Lukka from his thoughts. He followed them to the other side of a ridge. Down below, he could see a woman wearing immaculate robes facing a group of masked individuals. Purple, wispy smoke curled and danced across their covered features; all wore hoods, turning their silhouette alien and inhuman.
The woman didn't appear concerned to be outnumbered four to one. Stitched onto her robes, Lukka could make out the stylized form of a dragon. #emph[Ah, the Dragonsguard I've heard so much about.] Elite mages that had studied at the beck and claw of those scaly old reptiles.
"This is your last chance," the woman was saying. "Turn yourself in and—"
The masked figures didn't wait for her to finish. One shot out a hand, a coil of dripping purple energy snapping out toward her. The Dragonsguard flicked her wrist effortlessly; there was a bright flash, and suddenly the coil of dark magic was flying—
Right for Lukka.
He ducked just in time, the spell hissing horribly as it flew overhead and hit a tree to his right. At once, the truck began to blacken as rot spread out from the point of impact. Bits of dead leaves rained down on the clearing, and the sound of cracking wood signaled imminent collapse. Lukka leapt out of the way just as the top of the tree split off and landed where he'd been standing.
#emph[That could have killed me.] He couldn't decide who to be mad at—the one who'd cast the spell in the first place or the one who'd redirected it toward him. He settled on both.
Lukka cast his senses out into the forest, snagging on a bear claws-deep in a berry bush. Further: his senses grabbed the wolves dozing as they waited for nightfall, and he jerked them to wakefulness. Further still, he felt the strange fervor of a creature that had already been creeping toward the clearing, drawn by the lure of~magic? Lukka frowned but kept his focus. Connecting with the nearby beasts, he summoned each and every one to the clearing.
The Oriq agents, meanwhile, spread out to surround the Dragonsguard. One of them threw a ball of crackling black flame toward her; with a gesture, she turned it to stone, and it dropped out of the air harmlessly. Another conjured what looked like a snake made of glittering, silvery liquid; with a spoken word, the Dragonsguard caused a massive clod of dirt and grass—shaped surprisingly like a mongoose—to rip its way free of the ground before pouncing on the arcane serpent. Even Lukka found himself impressed by how effortlessly she seemed to answer whatever spells they could throw at her.
Behind her, a wolf pounced from the treeline, teeth bared savagely. This one almost seemed to catch the woman by surprise—but before it could reach her throat, she sealed the beast in a greenish bubble. It floated off into the air, raging helplessly against its containment.
"So it's true," said the Dragonsguard, turning to look at him up on the ridge. "We had heard of an Oriq with your abilities."
"For the last time, I'm not a damn Oriq!" growled Lukka.
As if to drive home his point, the bear burst forth from the trees by the line of masked figures, sending them scrambling as it swiped wildly with those huge killing claws. One of them threw a hex over his shoulder as he fled, withering the animal's arm and causing it to roar in pain.
The sound was joined by a far less familiar sound. Lukka looked over to see the strange creature with whom he had connected burst forth from the treeline. It skittered across the clearing on six legs, disturbingly quick. Glowing tendrils waved from its head as if underwater. With single-minded focus, it made straight for the Dragonsguard.
This was a foe she seemed to take seriously. Lukka watched her set her feet and contort her hands in an arcane position. She spoke a word, and roots as thick as his arm burst forth from the ground, wrapping around the chitinous legs of the creature. He heard the snapping of limbs as it was dragged down into the earth, screeching all the while, until the soil covered the insectile thing with an awful finality.
Lukka was so drawn in by the spectacle, he didn't notice the root creeping around his own ankle until it yanked him into the soil down to his waist. He pressed on either side of himself, trying to lift himself free, but to no effect. The Dragonsguard sauntered over to him, clearly in no rush.
"Neat trick. But, at the end of the day, you're nothing but an untrained hedge-mage, like any other Oriq." She extended an open palm toward him.
Something blurred at the edge of Lukka's vision. A second later, the Dragonsguard screamed. There was a blooming of heat and a bright wash of flame, and he turned away, shielding his face with one hand. When he looked back, a familiar shape stood over the Dragonsguard's still body, her fiery tail twitching as she sniffed at her fallen opponent. When she was satisfied, the foxlike creature turned and looked at Lukka, her big eyes oddly knowing.
Lukka held the beast's gaze for a moment before looking around the clearing. The Oriq agents were gone. If he hadn't been there, they wouldn't have lasted more than a minute. No discipline, no strategy. Just a bunch of scary costumes.
Lukka dragged himself to his feet and scanned the ground nearby. Obviously, the Oriq agents had left a trail in their haste to get away; he easily spotted the signs the masked mages had left in their wake. #emph[If everyone who doesn't play by the rules here is an Oriq, maybe I'm one of them after all.]
He was about to start following the trail when a soft yelp made him pause. Lukka turned to find the foxlike creature sitting in the clearing. She blinked and cocked her head to one side.
Lukka turned and shook his head, resigned. "Fine."
He closed his eyes and reached out with his mind. The fox's own mind seemed to leap to meet his, and the bond softly slipped back into place. Lukka let himself relive the sense of relief and gratitude he'd felt when he'd seen her fly at the guard.
He opened his eyes to find the creature watching him, her tongue hanging over the side of her blood-stained maw. She trotted over to the Oriq's trail and sniffed at one of the tracks.
"Well. If you're going to stick around, then I'll need to call you something. How about Mila?" He felt the pleasant ring of recognition in her mind and nodded. "Alright, then. Mila it is."
#v(0.35em)
#line(length: 100%, stroke: rgb(90%, 90%, 90%))
#v(0.35em)
Extus held his breath as he poured the shimmering red liquid into the shallow bowl. It swirled into the glowing potion, arcane light welling up in strange bubbles and casting strange shadows across the walls of the cave. The red lightened until it was nearly white—then violet shot through the mixture and the potion dimmed until it was nothing more than inert dark sludge. He smacked the bowl across the room, and it shattered against the wall, leaving the failed potion smeared across the stone. #emph[That was the fourth failure.]
Movement caught his eye, and Extus looked toward the entrance to the cave. One of his Oriq agents stood there, the dark magic flaring around their mask an unpleasant reminder.
"Why are you just standing there? Bring me more cervidar essence!"
The agent jumped as if physically struck and backed away from the cave, disappearing into the tunnel that led to the main cavern.
Alone, Extus slumped over his worktable. He looked over the books spread open before him. None of them had been any use. None of them showed him how to attain the power he needed. His gaze wandered over the side of the table to the floor, where the other ritual components lay still. The mage hunter's legs were still pinned down, held in the grip of the Oriq agents who now lay dead around it. All valuable tools, sacrificed for nothing—every last bit of life drained from their bodies, and it wasn't enough.
Someone entered the chamber behind him, and Extus straightened. "Are the rest of my supplies here?"
"There has been a delay. They ran into a Dragonsguard," said the agent.
Behind his mask, Extus gritted his teeth together. He reserved a special hatred for the Dragonsguard. Of all the meddlers who stood in his way, they were by far the worst. So arrogant, so self-assured. He was eager to show them just how misplaced all that confidence was—the Dragonsguard, and all the rest of Strixhaven's elite with them.
Not a day went by where he didn't think about that place. He could still remember walking through the Hall of Oracles. He could still see the space where his statue should have been. Just to the left of~
The Snarl.
Extus looked at the sludge, now dried on the wall. If more power was what he needed, that overlapping tangle of power hidden away below the school would offer more than enough, though reaching it would be no easy feat. That nexus of ancient energies wasn't some dusty book sitting on a shelf in the Biblioplex; it would be guarded by the most formidable forces Strixhaven could muster. Constructs, elementals, professors—Dragonsguard.
"There was someone else there," said the agent, drawing Extus from his thoughts. "Someone interfering."
She told him about the man who seemed able to call beasts of the forest to do his bidding. By the time she finished, Extus was more than intrigued.
"They say that he's following them now," the agent said. "Should I tell them to get rid of him?"
"No." Extus cleared his throat. He glanced at the bodies next to his table, then lifted his gaze toward the shadows overhead. The torchlight shone on the hard exoskeletons of the dormant mage hunters as they hung from the rocky ceiling. "Let him come."
Behind his mask, Extus smiled.
#v(0.35em)
#line(length: 100%, stroke: rgb(90%, 90%, 90%))
#v(0.35em)
Liliana set down the tome she had been studying and rubbed her eyes. Another day of fruitless research. She had done all that she could think of, and none of it would work. There wasn't a book or scroll or spell in Strixhaven that could bring Gideon back. Besides, with the Oriq on the move, there were more pressing matters at hand. Nobody else seemed to be taking them seriously.
#figure(image("003_Episode 2: Lessons/04.jpg", width: 100%), caption: [Confront the Past | Art by: <NAME>], supplement: none, numbering: none)
She glanced out the window behind her desk. In the distance, the suns had begun their slow descent toward the horizon. Light glinted off the floating stones of the Dawnbow. Liliana stared at the star arch, her gaze tracing its curve down toward the buildings of the main campus.
She'd come here to find a way to bring Gideon back. Nothing more and nothing less. But if she hadn't been here, she wouldn't have seen that Oriq agent in the Biblioplex. Liliana hated the idea of destiny. She'd always thought of it as someone else telling her what to do; just another heartless master. Gideon, however, had been a great believer in being in the right place at the right time. Maybe it was time she learned a lesson from him. #emph[Not too late, I hope.]
There was only so much she could do alone, though. Even if the mage students spent their free time blasting each other across the campus, they weren't prepared for what was coming. She needed help. She needed power.
A flash of gold outside her window caught her eye. Liliana leaned forward.
A group of young students ambled past her office. One of them stood out, her blond hair shining in the dim light as it fell over the shoulders of her Prismari uniform. <NAME> held her Witherbloom friends' attention as she gestured wildly, her sword bouncing against her leg as she led the group further down the walkway and out of sight.
Liliana sat back in her seat. #emph[Maybe it's time to take my role as a Professor a little more seriously.]
|
|
https://github.com/barddust/Kuafu | https://raw.githubusercontent.com/barddust/Kuafu/main/src/test.typ | typst | #import "mathenv.typ": *
#show: mathenv-init
#set heading(numbering: "1.")
= H1
== H2
#definition[
#lorem(20)
]
#example[
#lorem(10)
]
#proof[
#lorem(30)
]
#remark[
#lorem(10)
]
#proposition[
#lorem(20)
]
#solution[
#lorem(30)
$ f(b) - f(a) = f'(xi)(b-a) $
]
#theorem[
#lorem(20)
]
== H21
#theorem(name: "维尔斯特拉斯")[
#lorem(20)
]
#lemma[
]
= H11
#theorem[
#lorem(20)
]
|
|
https://github.com/gabrielrovesti/UniPD-Swiss-Knife-Notes-Slides | https://raw.githubusercontent.com/gabrielrovesti/UniPD-Swiss-Knife-Notes-Slides/main/Slides/UniPD%20Typst/slides.typ | typst | MIT License | #import "@preview/polylux:0.3.1": *
#import "unipd.typ": *
#show: unipd-theme.with(author: "<NAME>", date: "20/04/2023")
#set text(font: (
"Noto Sans",
"Segoe UI",
"roboto",
"Helvetica Neue",
"Cantarell",
"sans-serif",
))
#title-slide(
title: "Random title",
subtitle: "Discussione Tesi LT Informatica",
)
#slide(
title: "About this presentation",
new-section: "Introduction",
)[
This presentation is supposed to briefly showcase
what you can do with this package.
For a full documentation, read the #link(
"https://andreaskroepelin.github.io/polylux/book/",
)[online book].
]
#slide(
title: "A title",
)[
Let's explore what we have here.
On the top of this slide, you can see the slide
title.
We used the `title` argument of the `#slide`
function for that: ```typ
#slide(title: "First slide")[
...
]
```
(This works because we utilise the `clean` theme;
more on that later.)
]
#slide[
Titles are not mandatory, this slide doesn't have
one.
But did you notice that the current section name
is displayed above that top line?
We defined it using #raw(
"#new-section-slide(\"Introduction\")",
lang: "typst",
block: false,
).
This helps our audience with not getting lost
after a microsleep.
You can also spot a short title above that.
]
#slide(
title: "The bottom of the slide",
)[
Now, look down!
There we have some general info for the audience
about what talk they are actually attending right
now.
You can also see the slide number there.
]
#slide(
title: "Random text",
new-section: "Dynamic content",
)[
#lorem(64)
]
#slide(
title: [A dynamic slide with `pause`s],
)[
Sometimes we don't want to display everything at
once. #pause
That's what the `#pause` function is there for! #pause
It makes everything after it appear at the next
subslide.
#text(
.6em,
)[(Also note that the slide number does not change
while we are here.)]
]
#slide(
title: "Fine-grained control",
)[
When `#pause` does not suffice, you can use more
advanced commands to show or hide content.
These are some of your options: - `#uncover`
- `#only`
- `#alternatives`
- `#one-by-one`
- `#line-by-line`
Let's explore them in more detail!
]
#let example(body) = block(
width: 100%,
inset: .5em,
fill: aqua.lighten(80%),
radius: .5em,
text(size: .8em, body),
)
#slide(
title: [`#uncover`: Reserving space],
)[
With `#uncover`, content still occupies space,
even when it is not displayed.
For example, #uncover(2)[these words] are only
visible on the second"subslide".
In `()` behind `#uncover`, you specify _when_ to
show the content, and in `[]` you then say _what_
to show: #example[
```typ
#uncover(3)[Only visible on the third "subslide"]
```
#uncover(3)[Only visible on the third"subslide"]
]
]
#slide(
title: "Complex display rules",
)[
So far, we only used single subslide indices to
define when to show something.
We can also use arrays of numbers ...
#example[
```typ
#uncover((1, 3, 4))[Visible on subslides 1, 3, and 4]
```
#uncover((1, 3, 4))[Visible on subslides 1, 3, and 4]
]
...or a dictionary with `beginning` and/or `until`
keys: #example[
```typ
#uncover((beginning: 2, until: 4))[Visible on subslides 2, 3, and 4]
```
#uncover(
(beginning: 2, until: 4),
)[Visible on subslides 2, 3, and 4]
]
]
#slide(
title: "Convenient rules as strings",
)[
As as short hand option, you can also specify
rules as strings in a special syntax.
Comma separated, you can use rules of the form #table(
columns: (auto, auto),
column-gutter: 1em,
stroke: none,
align: (x, y) => (right, left).at(x),
[`1-3`],
[from subslide 1 to 3 (inclusive)],
[`-4`],
[all the time until subslide 4 (inclusive)],
[`2-`],
[from subslide 2 onwards],
[`3`],
[only on subslide 3],
)
]
#slide(
title: [`#only`: Reserving no space],
)[
Everything that works with `#uncover` also works
with `#only`.
However, content is completely gone when it is not
displayed.
For example, #only(2)[#text(red)[see how]] the
rest of this sentence moves.
Again, you can use complex string rules, if you
want. #example[
```typ
#only("2-4, 6")[Visible on subslides 2, 3, 4, and 6]
```
#only("2-4, 6")[Visible on subslides 2, 3, 4, and 6]
]
]
#slide(
title: [`#alternatives`: Substituting content],
)[
You might be tempted to try #example[
```typ
#only(1)[Ann] #only(2)[Bob] #only(3)[Christopher] likes #only(1)[chocolate] #only(2)[strawberry] #only(3)[vanilla] ice cream.
```
#only(1)[Ann] #only(2)[Bob] #only(3)[Christopher]
likes #only(1)[chocolate] #only(2)[strawberry] #only(3)[vanilla]
ice cream.
]
But it is hard to see what piece of text actually
changes because everything moves around. Better: #example[
```typ
#alternatives[Ann][Bob][Christopher] likes #alternatives[chocolate][strawberry][vanilla] ice cream.
```
#alternatives[Ann][Bob][Christopher] likes #alternatives[chocolate][strawberry][vanilla]
ice cream.
]
]
#slide(
title: [`#one-by-one`: An alternative for `#pause`],
)[
`#alternatives` is to `#only` what `#one-by-one`
is to `#uncover`.
`#one-by-one` behaves similar to using `#pause`
but you can additionally state when uncovering
should start. #example[
```typ
#one-by-one(start: 2)[one ][by ][one]
```
#one-by-one(start: 2)[one][by][one]
]
`start` can also be omitted, then it starts with
the first subside: #example[
```typ
#one-by-one[one ][by ][one]
```
#one-by-one[one][by][one]
]
]
#slide(
title: [`#line-by-line`: syntactic sugar for `#one-by-one`],
)[
Sometimes it is convenient to write the different
contents to uncover one at a time in subsequent
lines.
This comes in especially handy for bullet lists,
enumerations, and term lists. #example[
#grid(
columns: (1fr, 1fr),
gutter: 1em,
```typ
#line-by-line(start: 2)[
- first
- second
- third
]
```,
line-by-line(
start: 2,
)[
- first
- second
- third
],
)
]
`start` is again optional and defaults to `1`.
]
#slide(
title: [`#list-one-by-one` and Co: when `#line-by-line`
doesn't suffice],
)[
While `#line-by-line` is very convenient
syntax-wise, it fails to produce more
sophisticated bullet lists, enumerations or term
lists. For example, non-tight lists are out of
reach.
For that reason, there are `#list-one-by-one`, `#enum-one-by-one`
, and `#terms-one-by-one`, respectively. #example[
#grid(
columns: (1fr, 1fr),
gutter: 1em,
```typ
#enum-one-by-one(start: 2, tight: false, numbering: "i)")[first][second][third]
```,
enum-one-by-one(
start: 2,
tight: false,
numbering: "i)",
)[first][second][third],
)
]
Note that, for technical reasons, the bullet
points, numbers, or terms are never covered.
`start` is again optional and defaults to `1`.
]
#slide(
title: "How a slide looks...",
new-section: "Themes",
)[
... is defined by the _theme_ of the presentation.
This demo uses the `unipd` theme.
Because of it, the title slide and the decoration
on each slide (with section name, short title,
slide number etc.) look the way they do.
Themes can also provide variants, for example ...
]
#focus-slide[
... this one!
It's very minimalist and helps the audience focus
on an important point.
]
#slide(
title: "Your own theme?",
)[
If you want to create your own design for slides,
you can define custom themes!
#link(
"https://andreaskroepelin.github.io/polylux/book/themes.html#create-your-own-theme",
)[The book]
explains how to do so.
]
#slide(
title: [The `utils` module],
new-section: "Utilities",
)[
Polylux ships a `utils` module with solutions for
common tasks in slide building.
]
#slide(
title: [Fit to height],
)[
You can scale content such that it has a certain
height using `#fit-to-height(height, content)`:
#fit-to-height(2.5cm)[Height is `2.5cm`]
]
#slide(
title: "Fill remaining space",
)[
This function also allows you to fill the
remaining space by using fractions as heights,
i.e. `fit-to-height(1fr)[...]`:
#fit-to-height(1fr)[Wow!]
]
#slide(
title: "Side by side content",
)[
Often you want to put different content next to
each other. We have the function `#side-by-side`
for that:
#side-by-side(lorem(10), lorem(15), lorem(12))
]
#slide(
title: "Outline",
)[
Why not include an outline? #polylux-outline(padding: 0.5em, enum-args: (tight: false))
]
#slide(
title: "Use Typst!",
new-section: "Typst features",
)[
Typst gives us so many cool things #footnote[For example footnotes!]
. Use them!
]
#slide(
title: "That's it!",
new-section: "Conclusion",
)[
Hopefully you now have some kind of idea what you
can do with this template.
Consider giving it #link(
"https://github.com/andreasKroepelin/polylux",
)[a GitHub star]
or open an issue if you run into bugs or have
feature requests.
]
|
https://github.com/soul667/typst | https://raw.githubusercontent.com/soul667/typst/main/PPT/typst-slides-fudan/themes/polylux/book/src/dynamic/alternatives-position.typ | typst | #import "../../../polylux.typ": *
#set page(paper: "presentation-16-9")
#set text(size: 40pt)
#polylux-slide[
We know that
#alternatives(position: center + horizon)[$pi$][$sqrt(2)^2 + 1/3$]
is
#alternatives[irrational][rational].
]
|
|
https://github.com/kdog3682/2024-typst | https://raw.githubusercontent.com/kdog3682/2024-typst/main/src/render-json.typ | typst |
const renderFunctionRef = {
table,
heading,
text,
block,
image,
figure,
box,
set,
}
|
|
https://github.com/csimide/SEU-Typst-Template | https://raw.githubusercontent.com/csimide/SEU-Typst-Template/master/seu-thesis/pages/statement-bachelor-ic.typ | typst | MIT License | #import "../utils/fonts.typ": 字体, 字号
#page(
paper: "a4",
margin: (
top: 2cm + 0.5cm,
bottom: 2cm + 0.5cm,
left: 2cm + 0.25cm,
right: 2cm + 0.25cm,
),
{
v(80pt - 0.4cm)
set align(left)
set text(font: 字体.宋体, size: 字号.小四, lang: "zh", region: "cn")
set par(leading: 11.3pt, justify: true, first-line-indent: 0pt)
set line(stroke: 0.6pt)
align(
center,
text(
font: 字体.黑体,
size: 字号.小二,
)[东南大学毕业（设计）论文独创性声明],
)
v(24pt)
h(2em)
[本人声明所呈交的毕业（设计）论文是我个人在导师指导下进行的研究工作及取得的研究成果。尽我所知，除了文中特别加以标注和致谢的地方外，论文中不包含其他人已经发表或撰写过的研究成果，也不包含为获得东南大学或其它教育机构的学位或证书而使用过的材料。与我一同工作的同志对本研究所做的任何贡献均已在论文中作了明确的说明并表示了谢意。]
v(18pt)
grid(
columns: 11,
h(48pt),
[论文作者签名：],
line(length: 8em, start: (6pt, 10pt)),
h(18pt),
[日期：],
line(length: 3.5em, start: (6pt, 10pt)),
[年],
line(length: 2.5em, start: (2pt, 10pt)),
[月],
line(length: 2.5em, start: (2pt, 10pt)),
[日],
)
v(140pt)
align(
center,
text(
font: 字体.黑体,
size: 字号.小二,
)[东南大学毕业（设计）论文使用授权声明],
)
v(13pt)
h(2em)
[东南大学有权保留本人所送交毕业（设计）论文的复印件和电子文档，可以采用影印、缩印或其他复制手段保存论文。本人电子文档的内容和纸质论文的内容相一致。除在保密期内的保密论文外，允许论文被查阅和借阅，可以公布（包括刊登）论文的全部或部分内容。论文的公布（包括刊登）授权东南大学教务处办理。]
v(16pt)
grid(
columns: (24pt, 200pt, 22pt, 1fr),
row-gutter: 10pt,
rows: 2,
[],
grid(
columns: 2,
[论文作者签名：],
line(length: 115pt, start: (6pt, 10pt)),
),
[],
grid(
columns: 2,
[导师签名：],
line(length: 140pt, start: (6pt, 10pt)),
),
[],
grid(
columns: 7,
[日期：],
line(length: 3.5em, start: (6pt, 10pt)),
[年],
line(length: 2.9em, start: (2pt, 10pt)),
[月],
line(length: 2.9em, start: (2pt, 10pt)),
[日],
),
[],
grid(
columns: 7,
[日期：],
line(length: 2.5em, start: (6pt, 10pt)),
[年],
line(length: 2.9em, start: (2pt, 10pt)),
[月],
line(length: 2.9em, start: (2pt, 10pt)),
[日],
),
)
},
) |
https://github.com/ngoetti/knowledge-key | https://raw.githubusercontent.com/ngoetti/knowledge-key/master/template/sections/01-introduction.typ | typst | MIT License | #import "../utils.typ": *
= Introduction Cloud Operations and DevOps
== The DevOps pipelines
*What is DevOps?*\
DevOps team focuses on CI/CD. DevOps team would like to be continuously pushing small changes out to production, monitor what happens in production, see he result of that and use that to make further improvements to the system.
*Plan stage*: Backlog filled, Sprint Planning\
*Code stage*: Code is written, reviewed, and merged\
*Build stage*: CI Pipeline builds code and runs tests\
*Test stage*: Deploy to test environment, run automated tests\
*Release stage*: Tag code snapshot, Document features and changes\
*Deploy stage*: Deploy to production environment, Monitor\
*Operate Stage*: Ensuring application runs smootly, troubleshoot problems
*Monitor Stage*: Monitor and logging\
== The Devops lifecycle
#figure(
image("../figures/devops-lifecycle.png", width: 100%),
caption: [
DevOps Stages
],
)
*Continuous integration*
- Commit early, commit often
- Push code to the repository in the smallest possible size
- Push code to the repository frequently
- CI testing (DAST - Dynamic Application Security Testing, Unit Tests, Code Coverage)
*Continuous delivery & deployment*
- Testing/Production Environments are provisioned and configured
- Continuous Delivery requires a trigger to deploy the application while in Continuous Deployment this is automated.
- Verify how the application works under load
- Strategies: Rolling deployment: Deploy in groups. Blue-Green deployment: Deploy a new version alongside the old one. Canary deployment: Deploy to a subset of users
*Continuous Feedback*
- Happens at the beginning and end of the continuous lifecycle
- Metrics, statistics, analytics, and feedback from the customer and
teams involved are considered to continuously improve the product
== DevOps in GitLab CI
GitLab CI is a Continuous Integration server built right into GitLab
- Build, test and deploy code automatically on every change
- Keep building scripting together with the code
- Works on gitlab.com or your GitLab server
*Building and testing with Docker*\
Building a docker image from within a docker container that the GitLab Ci is running for us.\
A docker registry is built into the repository (`$CI_REGISTRY`) `$CI_REGSITRY_IMAGE` is the path where the build image is going to be located.
Use docker login to login into the registry using the `$CI_JOB_TOKEN`
#sourcecode[```yaml
stages:
- build
- test
- deploy
variables:
DOCKER_IMAGE_TAG: $CI_REGISTRY_IMAGE:$CI_COMMIT_SHORT_SHA
build:
stage: build
image: docker:stable
services:
- docker:dind
variables:
DOCKER_HOST: tcp://docker:2375/
DOCKER_DRIVER: overlay2
before_script:
- docker login -u gitlab-ci-token -p $CI_JOB_TOKEN $CI_REGISTRY
- docker info
script:
- docker build -t $DOCKER_IMAGE_TAG .
- docker push $DOCKER_IMAGE_TAG
test:
stage: test
image: node:10
services:
- name: postgres:10
```]
== DevOps with GitLab CI: Build stages, artifacts, and dependencies
*Using build stages*\
Each stage contains one or more jobs.
Stages are run in the order they are declared.
Any job failure marks the stage as failed.
When you do not declare stages, the default stages are
- build
- test
- deploy
*Running build steps in parallel*\
By assigning two jobs to the same stages, Gitlab CI runs the two jobs in parallel together.
The parallel tag creates copies of the same job and runs them in parallel.
*Speeding up builds with the cache*\
We can specify paths to cache the modules and speed up future builds. (The `$CI_COMMIT_REF_SLUG` is a variable that identifies the branch.)
This Variable can be used to reference the cache folder from the branch.
#sourcecode[```yaml
cache:
key: $CI_COMMIT_REF_SLUG
paths:
- node_modules/
```]
*Defining artifacts*\
We can define artifacts of files we would like to keep.
You can configure it to only keeping artifacts when a job has succeeded.
Artifacts can be used in future jobs of the pipeline and downloaded via the Gitlab web interface or API.
In the .gitlab-ci.yml, a new key “artifacts is defined.
#sourcecode[```yaml
artifacts:
paths:
- package-lock.json
- npm-audit.json
```]
The key when can be added.
3 options
- On success
- On failure
- Always
The default is on success
*Using artifacts in future stages*\
By default, any artifacts produced in one job is going to be available to the other jobs.
- The test job will get both artifacts (because it has no explicit dependencies)
- The test2 job will get only the artifact from the build2 (because of the dependency)
#grid(
columns: (auto, auto),
sourcecode[```yaml
build:
stage: build
script:
- echo "I am an artifact" > artifact.txt
artifacts:
paths:
- artifact.*
build2:
stage: build
script:
- echo "I am also an artifact" > artifact2.txt
artifacts:
paths:
- artifact2.*
```],
sourcecode[```yaml
test:
stage: test
script:
- cat artifact*.*
test2:
stage: test
dependencies:
- build2
script:
- cat artifact2.*
```]
)
*Passing variables to builds*\
There are a few ways to define variables for a script:
- Per step in the pipeline definition
- Globally for all steps in the pipeline definition
- When executing a pipeline manually
- On repository level
- On group level
These variables are available as environment variables during the build. |
https://github.com/nicolasfara/Curriculum-Vitae | https://raw.githubusercontent.com/nicolasfara/Curriculum-Vitae/master/common.typ | typst | Apache License 2.0 | #import "@preview/fontawesome:0.1.0": *
#let line-spacing = 0.75em
#let entries-spacing = 0.65em
#let main-color = rgb(167, 199, 231).darken(30%)
#let separation-line() = box(inset: (top: 0.2em, bottom: 0.2em), line(length: 100%, stroke: (dash: "dotted", paint: gray)))
// #let separation-line() = repeat(text(fill: gray)[-])
#let with-small-right-column(left, right) = grid(
columns: (1fr, auto),
column-gutter: 2em,
left,
right
)
#let show-contact-entry(contact-entry) = stack(
dir: ltr,
spacing: 1.5em,
stack(
dir: ltr,
spacing: 0.6em,
move(dy: -0.15em, dx: 0.30em, contact-entry.icon-path),
contact-entry.content
)
)
#let show-contact-entries(entries) = entries.map(entry => box(inset: 0.4em, show-contact-entry(entry))).join(" ")
#let show-header(name, contact-entries, image-path) = with-small-right-column(
[
#text(size: 2em)[= #name]
#align(center)[#show-contact-entries(contact-entries)]
],
if image-path != "none" [#move(dy: -1em, image-path)]
)
#let section-title(title) = text(fill: main-color, size: 1.2em)[
== #title
#line(length: 100%, stroke: 0.1em + main-color)
]
#let subsection-title(title) = text(fill: main-color, size: 1.2em)[
=== #title
//#line(length: 100%, stroke: 0.1em + main-color)
]
#let entry-title(title) = text(size: 1.1em)[=== #title]
#let show-entry(entry) = {
let subtitle = [
#entry.subtitle #if "subtitle-aside" in entry.keys() [
--- #entry.subtitle-aside
]
]
let content = (
with-small-right-column(entry-title(entry.title), if "date" in entry.keys() { emph(entry.date) } else { [] }),
emph(subtitle),
)
if "more" in entry.keys() { content.push(block(inset: (top: 0.3em), entry.more)) }
stack(
dir: ttb,
spacing: line-spacing,
..content
)
}
#let intersperse(array, elem) = {
let result = ()
for entry in array {
result.push(entry)
result.push(elem)
}
result.slice(0, result.len() - 1)
}
#let show-entries(entries) = stack(
dir: ttb,
spacing: entries-spacing,
..intersperse(entries.map(show-entry), separation-line()),
box(inset: (bottom: 0.25em))
)
// #let pill(content) = box(
// rect(
// stroke: gray,
// radius: 50%,
// text(fill: gray.darken(70%), content)
// )
// )
#let card(content) = box(
inset: (right: 0.5em),
rect(
stroke: gray,
radius: 0.5em,
fill: gray.lighten(90%),
text(fill: gray.darken(70%), content)
)
)
#let section(title, content) = stack(
dir: ttb,
spacing: line-spacing,
section-title(title),
content
)
#let section-elem(title, content) = stack(
dir: ttb,
spacing: line-spacing,
section-title(title),
..content
)
#let entries-section(title, entries) = section(title, show-entries(entries))
#let pill-section(title, pills) = section-elem(title, pills.pairs().map(elem => stack(
dir: ttb,
spacing: 1em,
subsection-title(elem.at(0)),
elem.at(1).map(card).join(" ")
))) |
https://github.com/Tiggax/zakljucna_naloga | https://raw.githubusercontent.com/Tiggax/zakljucna_naloga/main/dispozicija/dispozicija.typ | typst | #import "additional.typ": todo
#let naslov = [
Matematični model bioreaktorja CHO celic z dovajanjem
]
#let structure = [
The first chapter is devoted to the introduction, where we will present the basic assumptions and methods we will use.
In the second chapter we will cover information about bioreactors, their types and their classifications. The chapter will also cover types of cells used in the bioreactors.
Third chapter focuses on the modeling of bioreactors. It will cover Mass balance, cell metabolism in the bioractor, monod kinetics and different process controls.
The fourth chapter will talk about Numerical methods, their function, use and will go into depth about Euler and Runge-Kutta methods.
In the Fifth chapter, we will describe the mathematical bioreactor model, operational parameters of the model, and regression analysis of the model.
Sixth chapter talks about the objectives of the work.
Seventh chapter will describe the methods used to construct the system, and each of the variables in the model. In this chapter we will also talk about total balance of the system.
In the eight chapter and ninth chapter will be intended for Results and the Conclusion of the work.
The tenth chapter will be a summary of the work in slovene language as per rulebook guidelines for english work.
Content:
+ Introduction
+ Bioreactors
+ Types
+ Batch
+ Fed-batch
+ Bioreactors with CHO cells
+ CHO cells
+ Bioreactor Modeling
+ Mass balance
+ Cell metabolism
+ Monod kinetics
+ Process control
+ Numerical methods
+ Euler's method
+ Runge-Kutta method
+ Model
+ Mathematical model Development
+ Operational parameters
+ Regression analysis
+ Objectives
+ Methods
+ System
+ Viable Cell Density
+ Glucose
+ Glutamine
+ Oxygen
+ Total balance
+ Results
+ Conclusion
+ Summary (in Slovene)
]
#align(center, text(upper(naslov), size: 1.5em))
#align(center)[<NAME>]
Bioreactors with CHO (Chinese Hamster Ovary) cell cultures are used in the pharmaceutical industry to produce various metabolic products. Research and development of these cell cultures represent a significant cost for studying the operation of bioreactors under different parameters. The use of mathematical models can reduce costs and save time required for industrial production. The task involves using systems of ordinary differential equations to simulate the process within the bioreactor. The created model would then be calibrated using hypothetical data from a smaller research reactor and subsequently simulate the process of a larger, industrial reactor.
The work has been carried out since mid-March at Novartis Mengeš, under the supervision of mentor <NAME>. The planned completion of the project is in mid-August.
#structure
#bibliography("dispo.bib", full: true, title: [Sources])
#pagebreak()
<NAME> je zaposleni Kemični inžinir v Novartis d.o.o.. Deluje v poddružnici Novartis - Mengeš.
deluje na oddelku za biološke procese, kjer vodi oddelek za simulacije bioprocesov.
Doktoriral je na Univerzi v ljubljani, na fakulteti za Kemijo in kemijsko tehnologijo. Kot raziskovalec je sodeloval v Kemijskem inštitutu.
|
|
https://github.com/PA055/5839B-Notebook | https://raw.githubusercontent.com/PA055/5839B-Notebook/main/README.md | markdown | ## Installation
> This installation process is temporary, as we wait for Typst to overhaul its process for packaging templates and packages.
The best way to install the Notebookinator is as a local package. Make sure you
have the following software installed on your computer:
- [Typst](https://github.com/typst/typst#installation)
- [Git](https://github.com/casey/just#installation)
- [VSCode](https://code.visualstudio.com)
- [just](https://github.com/casey/just#installation)
Once you've installed everything, simply run the following commands:
```bash
git clone https://github.com/BattleCh1cken/notebookinator
cd notebookinator
just install
```
> If you're running this on Windows, you'll need to run these commands in a sh shell, like git-bash or the shell packaged with Cygwin or GitHub Desktop.
## Making New Entries
To create a new entry you first need to create a new `.typ` file in the `entries/` folder. There are two different ways this project organizes entries. Either they are organized by project section (for example flywheel, or intake), or they are single entries.
To create a single entry, create a file with this path: `entries/<entry-name>/entry.typ`.
To create an entry in a group, create a file with the following path: `entries/<group-name>/<entry_name>.typ`
Once you've done this, you need to create an entry in the file.
```typ
#import "/packages.typ": notebookinator
#import notebookinator: *
#import themes.radial.components: *
#show: create-body-entry.with(
title: "<EDP Stage>: <your title here>",
type: "<EDP Stage>",
date: datetime(year: 1982, month: 1, day: 1),
author: "<NAME>",
witness: "Davis Bodami",
)
Write your content here.
```
Make sure to read through the [Notebookinator](https://github.com/BattleCh1cken/notebookinator) documentation to see what components and options you can use while writing entries. You can also look at other existing entries as examples.
Once you're happy with your entry you'll need to add it to the entry index at `entries/entries.typ`, so that the `main.typ` file is aware of it.
Add the file to `entries/entries.typ` like this:
```typ
// Do this if its a single entry:
#include "./<entry_name>/entry.typ"
// Do this if its a group:
#include "./<group_name>/<entry_namge>.typ"
```
The order that the notebook renders the entries is dependent on the order that they're placed in this file, so make sure to put the `#include` in the correct spot.
|
|
https://github.com/soul667/typst | https://raw.githubusercontent.com/soul667/typst/main/PPT/typst-slides-fudan/themes/polylux/book/src/themes/gallery/bipartite.typ | typst | #import "../../../../polylux.typ": *
#import themes.bipartite: *
#show: bipartite-theme
#set text(size: 25pt)
#title-slide(
author: [Author],
title: [Title],
subtitle: [Subtitle],
date: [Date],
)
#west-slide(title: "A longer slide title")[
#lorem(40)
]
#east-slide(title: "On the right!")[
#lorem(40)
]
#split-slide[
#lorem(40)
][
#lorem(40)
]
|
|
https://github.com/UriMtzF/typst-templates | https://raw.githubusercontent.com/UriMtzF/typst-templates/main/README.md | markdown | MIT License | # typst-templates
Personal typst templates
|
https://github.com/TypstApp-team/typst | https://raw.githubusercontent.com/TypstApp-team/typst/master/tests/typ/bugs/math-eval.typ | typst | Apache License 2.0 | // Evaluating a math expr should renders the same as an equation
#eval(mode: "math", "f(a) = cases(a + b\, space space x >= 3,a + b\, space space x = 5)")
$f(a) = cases(a + b\, space space x >= 3,a + b\, space space x = 5)$
|
https://github.com/LilNick0101/Bachelor-thesis | https://raw.githubusercontent.com/LilNick0101/Bachelor-thesis/main/thesis.typ | typst | #import "./thesisHeader.typ": *
#import "@preview/minitoc:0.1.0": *
#import "@preview/glossarium:0.2.0": print-glossary, gls, glspl
#show: doc => mainPage(
[= Abstract
Questo documento descrive il lavoro svolto durante il periodo di stage della durata di 320 ore presso l'azienda _Zero12 s.r.l._
Lo scopo dello stage è stata la partecipazione al progetto _Smart Offices_ che consisteva nello sviluppo di una piattaforma per la consultazione, ricerca, caricamento e salvataggio di luoghi dove fare _smart working_; utenti registrati inoltre possono caricare recensioni dei luoghi con valutazioni. Io mi sono occupato di sviluppare l'applicazione mobile _Android_, che comunicava con il back-end _RestFul JSON_ sviluppato da altri colleghi.
L'applicazione è stata sviluppata usando tecnologie native _Android_, in particolare il linguaggio _Kotlin_ e il moderno toolkit di UI _Jetpack Compose_.
Inizialmente il progetto è stato preceduto da una parte di training dove si apprendevano i vari concetti fondamentali di _Kotlin_, di _Jetpack Compose_ e dell'architettura di un'applicazione _Android_ finendo con una breve demo per mettere in pratica ciò che è stato appreso.
In seguito, si è proceduto con lo sviluppo effettivo dell'applicazione, con design dell'esperienza utente e codifica delle varie funzionalità dell'applicazione.
Si è usata una metodologia di lavoro agile, con stand-up giornalieri di 15 minuti per allinearsi con il lavoro fatto.
],
[= Ringraziamenti
_In primo luogo, ci tengo a ringraziare il relatore Prof. <NAME>, per avermi aiutato e sostenuto durante il mio lavoro._
_Ringrazio con affetto tutta la mia famiglia, per la vicinanza che mi hanno dato in qualsiasi momento del mio periodo di studio._
_Ringrazio inoltre tutti i collaboratori e i tirocinanti dell'azienda per la grande ospitalità e la disponibilità durante il periodo di tirocinio._
_Infine, ringrazio tutti gli amici e le persone che ho incontrato all'università che mi hanno accompagnato in questa avventura._],
doc
)
#set heading(numbering: "1.1.1")
#include "./content/introduction.typ"
#include "./content/project.typ"
#include "./content/RA.typ"
#include "./content/design.typ"
#include "./content/coding.typ"
#include "./content/conclusions.typ"
#counter(heading).update(0)
#counter(page).update(0)
#let appendices(body) = {
pagebreak()
counter(heading).update(0)
counter("appendices").update(1)
set heading(
numbering: (..nums) => {
let vals = nums.pos()
let value = "ABCDEFGHIJ".at(vals.at(0) - 1)
if vals.len() == 1 {
return ""
}
else {
return value + "." + nums.pos().slice(1).map(str).join(".")
}
}
);
[#body]
}
#show: appendices
#include "./content/appendix.typ"
#pagebreak()
#bibliography("./bibliography.yaml")
// MUST DO |
|
https://github.com/rabotaem-incorporated/probability-theory-notes | https://raw.githubusercontent.com/rabotaem-incorporated/probability-theory-notes/master/sections/04-discrete-random-processes/02-branching-processes.typ | typst | #import "../../utils/core.typ": *
== Ветвящиеся процессы
Пусть у нас есть какие-то частицы, которые разможаются, умирают, и т.д. С вероятностью $f_k$ частица превращается в $k$ частиц. Изначально частиц $eta_0 = 1$. На следующем шаге частиц $eta_1 = xi_1^((1))$, где $xi_k^((n))$ --- количество частиц, которые превратились в $k$-я частица на $n$-м шаге. Соответсвенно на втором шаге частиц будет $eta_2 = xi_1^((2)) + xi_2^((2)) + ... + xi_(eta_1)^((2))$. $P(xi_j^((n)) = k) = f_k$.
Давайте этот процесс изучать.
Пусть $F(t) = G_(xi_j^((n))) (t) = sum_(k = 0)^oo f_k t^k$. Хотим понять $G_(eta_n) (t)$. Согласно последнему примеру из предыдущего параграфа, это $G_(eta_(n - 1)) (F(t))$. То есть по индукции, это $G_n (t) = F(F(F(... F(t) ...)))$. Хотим узнать $E eta_n = G'_n (1)$, а $G_n (t) = G_(n - 1) (F(t))$. Тогда
$
G'_n (t) = G'_(n - 1) (F(t)) F'(t) ==> G'_n (1) = G'_(n - 1) (F(1)) F'(1) = a dot G'_(n - 1) (1) = a E eta_(n - 1).
$
Значит $E eta_n = a^n$.
#th[
Рассмотрим ветвящийся процесс с производящей функцией числа потомков $F$. Тогда вероятность его вырождения (то есть того, что в какой-то момент потомки исчезнут вообще) равна наименьшему положительному корню уравнения $F(x) = x$.
]
#notice[
$F$ возрастает на $[0, 1]$. $F'$ тоже, поэтому функция выпукла. А еще $F(1) = 1$, то есть наименьший положительный корень не больше $1$. Собственно, это корень, который получается в другой точке пересечения графика $F$ с прямой $y = x$ (если такая есть).
#TODO[картинка]
Если производная в единице, то есть матожидание $xi_j^((n))$ не больше $1$, то вероятность вырождения равна $1$, а при больших значениях --- что-то меньшее $1$.
]
#proof(name: "теоремы")[
$A_n = {eta_n = 0}$ -- событие того, что на $n$-м шаге никого не осталось. Очевидно, $... subset A_n subset A_(n + 1) subset ...$. Значит $P(A_1) <= P(A_2) <= P(A_3) <= ...$ --- а у таких последовательностей есть предел. Назовем его $q := lim P(A_n)$. Тогда
$
P(A_n) = P(eta_n = 0) = underbrace(G_(eta_n), := G_n) (0) = F compose G_(n - 1) (0).
$
Обозначим $q_n := P(A_n)$. Тогда $q_n = F(q_(n - 1))$. Значит
$
q = lim q_n = lim F(q_(n - 1)) = F(lim q_(n - 1)) = F(q).
$
Тогда $q$ --- корень уравнения $F(x) = x$. Пусть $y$ --- наименьший неотрицательный корень. Тогда $y >= 0$, и $F(y) >= F(0) = G_1 (0) = q_1$. По индукции проверим, что $q_n <= y$. База есть. Переход очевиден: $q_(n + 1) = F(q_n) <= F(y) = y$. Значит $q_n <= y$ для любого $n$, и $q = lim q_n <= y$. Значит $q = y$ (наименьший неотрицательный корень).
]
#follow[
Если $E xi_1 = 1$ и $D xi_1 > 0$, то вероятность вырождения равна $1$ (график $F$ касается $x = y$).
]
#th[
Пусть $E xi_1 = 1$, $0 < D xi_1 = sigma^2 < oo$, $q_n$ --- вероятность вырождения к $n$-ому шагу. $gamma_n := q_(n + 1) - q_n$ --- вероятность вырождения от $n$-го к $(n + 1)$-му поколению. Тогда
$
gamma_n sim 2/(sigma^2 n^2), quad 1 - q_n sim 2/(sigma^2 n).
$
]
#proof[
Введем обозначения:
$
q_n &:= P(eta_n = 0) = G_n (0) = F(q_(n - 1)), \
p_n &:= 1 - q_n, p_n = 1 - F(1 - p_(n - 1)), \
tilde(F) (x) &:= 1 - F(1 - x), p_n = tilde(F) (p_(n - 1)).
$
Разложим $tilde(F)$ в ряд:
$
tilde(F) (0) &= 1 - F(1) = 0, \
tilde(F)' (x) = (1 - F(1 - x))' = F'(1 - x) ==> tilde(F)' (0) &= F' (1) = E xi_1 = 1, \
tilde(F)''(x) = -F''(1 - x) ==> tilde(F)'' (0) &= -F''(1) = -D xi_1 = -sigma^2.
$
Тогда
$
tilde(F) (x) = x - (sigma^2 x^2)/2 + o(x^2).
$
Рассмотрим $a_n = 1/p_n$, а точнее
$
a_(n + 1) - a_n =
1/p_(n + 1) - 1/p_n =
(p_n - p_(n + 1))/(p_(n + 1) p_n) =
(p_n - tilde(F) (p_n))/(p_n tilde(F) (p_n)) =
(p_n - (p_n - (sigma^2 p_n^2)/2 + o(p_n^2)))/(p_n (p_n + o(p_n))) newline(=)
((sigma^2 p_n^2)/2 + o(p_n^2))/(p_n^2 + o(p_n^2)) = (sigma^2/2 + o(1))/(1 + o(1)) = sigma^2/2 + o(1) ==> a_n sim (n sigma^2)/2 ==> p_n = 1/a_n sim 2/(n sigma^2).
$
по теореме Штольца.
Распишем $gamma$:
$
gamma_n = q_(n + 1) - q_n = (1 - p_(n + 1)) - (1 - p_n) = p_n - p_(n + 1) = p_n - tilde(F)(p_n) newline(=) (sigma^2 p_n^2)/2 + o(p_n^2) sim (sigma^2 p_n^2)/2 sim sigma^2/2 dot (2/(n sigma^2))^2 = 2/(sigma^2 n^2).
$
]
|
|
https://github.com/saveriogzz/curriculum-vitae | https://raw.githubusercontent.com/saveriogzz/curriculum-vitae/main/modules_it/skills.typ | typst | Apache License 2.0 | #import "../brilliant-CV/template.typ": *
#cvSection("Competenze")
#cvSkill(
type: [Lingue],
info: [Inglese #hBar() Italiano]
)
#cvSkill(
type: [Tecnologie],
info: [Scala2 #hBar() Python #hBar() BigQuery]
)
#cvSkill(
type: [Interessi Personali],
info: [Nuoto #hBar() Apprendimento #hBar() Cibo]
)
|
https://github.com/Treeniks/bachelor-thesis-isabelle-vscode | https://raw.githubusercontent.com/Treeniks/bachelor-thesis-isabelle-vscode/master/chapters/02-background/lsp.typ | typst | #import "/utils/todo.typ": TODO
#import "/utils/isabelle.typ": *
#import "@preview/cetz:0.2.2"
== Language Server Protocol (LSP)
Before the introduction of the Language Server Protocol, it was common for code editors to either only support syntax highlighting for its supported languages with very basic auto-completion and semantic understanding or implement a full-fledged IDE for the language.
Now, the responsibility of semantic understanding of the language has moved entirely to the language server, while the language client is responsible for handling user interaction.
The goal is a system in which a new programming language only needs to implement a language server, while a new code editor only needs to implement a language client. In the best-case scenario, any language server and client can be used together (although, in practice, this is still not always the case). If we wanted to support $N$ programming languages for $M$ code editors, without the LSP, we would need $N dot M$ implementations of language semantics. With the LSP, this number is reduced drastically to only $N$ language server and $M$ language client implementations.
#cite(form: "prose", <lsp-spec>) describes the general setup: The client and server communicate via #box[`jsonrpc 2.0`] messages. The three primary message types are:
- _Notification Messages_
- _Request Messages_
- _Response Messages_
As the name suggests, notification messages only exist to notify the other party. They need not send a response back. Requests are sent to the other party and require a response message to be sent back once the request has been processed. The structure of these message types is also defined within the LSP specification and can be seen in @lsp-message-structure.
#figure(
{
set raw(lang: "ts")
table(
columns: 3,
// fill: (x, y) => if y == 0 { gray },
stroke: (x, y) => (
left: if x > 0 { .5pt } else { 0pt },
right: 0pt,
top: if y == 1 { .5pt } else { 0pt },
bottom: 0pt,
),
align: left,
table.header([*Notification*], [*Request*], [*Response*]),
[ `jsonrpc: string` ], [ `jsonrpc: string` ], [ `jsonrpc: string` ],
[], [ `id: integer | string` ], [ `id: integer | string | null` ],
[ `method: string` ], [ `method: string` ], [ `result?: Any` ],
[ `params?: array | object` ], [ `params?: array | object` ], [ `error?: ResponseError` ],
)
},
caption: [General LSP message structure.],
kind: table,
// placement: auto,
) <lsp-message-structure>
At the time of writing, The `jsonrpc` entry of every message is always set to "`2.0`". The `id` of the request is sent to identify the associated response. Thus, the `id` in a response message must also be set appropriately. The `method` entry is an identifier for the _kind_ of message at hand and dictates the shape of the `params`, `result`, and `error` entries, which in turn contain the primary data of the message.
There are many different _methods_. For example, messages dealing with text documents are sent under the #box["`textDocument/`"] method prefix, like the #box["`textDocument/hover`"] request, which requests for hover information, or the #box["`textDocument/didChange`"] notification, sent by the client to keep the server informed about changes made to the document's text.
=== Initialization <back:lsp-initialization>
Because of the LSP's server/client system, it is technically possible to use an externally running language server. Even so, in practice, the server is typically started by an IDE.
#figure(
cetz.canvas({
import cetz.draw: *
let r = 7
let m = (symbol: "stealth")
line((0, 0), (0, -3), name: "client")
content((rel: (0, .2), to: "client.start"), align(center)[Client\ (e.g. Editor)], anchor: "south")
line((r, 0), (r, -3), name: "server")
content((rel: (0, .2), to: "server.start"), align(center)[Server], anchor: "south")
line((0, -.5), (r, -.5), name: "connection2", mark: (end: m))
content((rel: (0, .2), to: "connection2.mid"), [`initialize` request])
line((0, -1.5), (r, -1.5), name: "connection3", mark: (start: m))
content((rel: (0, .2), to: "connection3.mid"), [`initialize` response])
line((0, -2.5), (r, -2.5), name: "connection4", mark: (end: m))
content((rel: (0, .2), to: "connection4.mid"), [`initialized` notification])
}),
caption: [Visualization of the LSP initialization handshake.],
kind: image,
placement: auto,
) <lsp-init>
The first message between client and server is an #box["`initialize`"] request sent by the client. The client has to wait for the server to respond to this request before sending any other messages. Finally, the client sends an #box["`initialized`"] notification to mark the initialization complete. This handshake is illustrated in @lsp-init.
Similarly to exchanging cipher suites in a TLS handshake, the client and server send each other their capabilities within the `initialize` request and response. These capabilities describe which features of the LSP the client or server actually supports. For example, not every server supports completions. Even if it does, further information is needed, like which characters should automatically request completions. By exchanging the capabilities this early on, the client and server can exclude certain parts of messages or even skip sending some entirely, preventing expensive JSON Serialization and Deserialization for messages that the other party cannot handle.
=== Isabelle Language Server
While the LSP defines most methods required for typical language server use cases, specific language servers may extend the basic protocol by their own methods. In such cases, the corresponding client needs to define extra handlers for these new methods.
Since the standard Language Server Protocol is designed with regular programming languages in mind, it defines little for other types of languages, particularly theorem provers @lsp-spec-extension. It is thus insufficient for Isabelle's needs. For example, to keep the output and state panels updated, the server must always know the current location of the caret. This is not a typical need for language servers of normal programming languages and is thus not built into the protocol by default.
Isabelle, therefore, extends the LSP with its own methods under the #box["`PIDE/`"] prefix, which have to be enabled with the #box["`vscode_pide_extensions`"] Isabelle option. For example, here are three such methods:
1. "`PIDE/caret_update`": A bidirectional notification telling the other party that the caret has been moved. Mostly sent from the client to the server.
2. "`PIDE/dynamic_output`": A notification sent from the server to the client containing the current content of the output panel.
3. "`PIDE/decoration`": A notification sent from the server to the client containing information on the dynamic syntax highlighting within the current theory.
There are several more of these methods. As a result, unlike most language servers, the Isabelle language server cannot be started from within an existing language client with the expectation that it will function correctly. Significant additional work needs to be done on the client side before an IDE can utilize the Isabelle language server.
|
|
https://github.com/MattiaOldani/Informatica-Teorica | https://raw.githubusercontent.com/MattiaOldani/Informatica-Teorica/master/capitoli/complessità/17_risorsa_tempo.typ | typst | #import "@preview/algo:0.3.3": algo, i, d, code
#import "@preview/lemmify:0.1.5": *
#let (
theorem, lemma, corollary,
remark, proposition, example,
proof, rules: thm-rules
) = default-theorems("thm-group", lang: "it")
#show: thm-rules
#show thm-selector("thm-group", subgroup: "theorem"): it => block(
it,
stroke: red + 1pt,
inset: 1em,
breakable: true
)
#show thm-selector("thm-group", subgroup: "proof"): it => block(
it,
stroke: green + 1pt,
inset: 1em,
breakable: true
)
#import "../alias.typ": *
= Definizione della risorsa tempo
_Come mai utilizziamo una DTM e non una macchina RAM per dare una definizione rigorosa di tempo?_
La risposta sta nella *semplicità*: le macchine RAM, per quanto semplici, lavorano con banchi di memoria che possono contenere dati di grandezza arbitraria ai quali accediamo con tempo $O(1)$, cosa che invece non possiamo fare con le DTM perché il nastro contiene l'input diviso su più celle.
== Definizione
Consideriamo la DTM $M = (Q, Sigma, Gamma, delta, q_0, F)$ e definiamo:
- $T(x)$ il *tempo di calcolo* di $M$ su input $x in Sigma^*$ come il valore
$ T(x) = \# "mosse della computazione di" M "su input" x "(anche" infinity")"; $
- $t(n)$ la *complessità in tempo* di $M$ (_worst case_) come la funzione
$ t : NN arrow.long NN bar.v t(n) = max{T(x) bar.v x in Sigma^* and abs(x) = n} . $
L'attributo *worst case* indica il fatto che $t(n)$ rappresenta il tempo _peggiore_ di calcolo su tutti gli input di lunghezza $n$. È la metrica più utilizzata anche perché è la più "manovrabile matematicamente", cioè ci permette di utilizzare delle funzioni più facilmente trattabili dal punto di vista algebrico. Ad esempio, nella situazione *average case* avremo una stima probabilmente migliore ma ci servirebbe anche una distribuzione di probabilità, che non è molto facile da ottenere.
Diciamo che il linguaggio $L subset.eq Sigma^*$ è riconoscibile in *tempo deterministico* $f(n)$ se e solo se esiste una DTM $M$ tale che:
+ $L = L_M$;
+ $t(n) lt.eq f(n)$.
L'ultima condizione indica che a noi _"basta"_ $f(n)$ ma che possiamo accettare situazioni migliori.
Possiamo estendere questa definizione anche agli insiemi o ai problemi di decisione:
- l'*insieme* $A subset.eq NN$ è riconosciuto in tempo $f(n)$ se e solo se lo è il linguaggio $ L_A = {cod(A) bar.v a in A} ; $
- il *problema di decisione* $Pi$ è risolto in tempo $f(n)$ se e solo lo è il linguaggio $ L_Pi = {cod(x) bar.v p(x)} . $
Da qui in avanti, quando parleremo di *linguaggi* intenderemo indirettamente *insiemi* o *problemi di decisione*, vista la stretta analogia tra questi concetti.
== Classi di complessità
=== Classificazione di funzioni
Tramite i simboli di Landau è possibile classificare le funzioni in una serie di classi.
Per quanto riguarda il tempo, data una funzione $t : NN arrow.long NN$ possiamo avere:
#align(center)[
#table(
columns: (30%, 40%, 30%),
inset: 10pt,
align: horizon,
[*Funzione*], [*Definizione formale*], [*Esempio*],
[*Costante*], [$t(n) = O(1)$], [Segno di un numero in binario],
[*Logaritmica*], [$f(n) = O(log(n))$], [Difficile fare esempi per questo perché quasi mai riusciamo a dare una risposta leggendo $log(n)$ input dal nastro],
[*Lineare*], [$f(n) = O(n)$], [Parità di un numero in binario],
[*Quadratica*], [$f(n) = O(n^2)$], [Stringa palindroma],
[*Polinomiale*], [$f(n) = O(n^k)$], [Qualsiasi funzione polinomiale],
[*Esponenziale*], [$f(n)$ non polinomiale ma super polinomiale], [Alcune funzioni super polinomiali sono $ e^n bar.v n! bar.v n^(log n) $]
)
]
L'ultima classe rappresenta una classe che costo _"troppo"_ elevato, ovvero una classe nella quale non vorremmo mai capitare. Qua dentro ci va tutto il calderone delle funzioni super polinomiali, che sono dette anche *inefficienti*.
Altrimenti, convenzionalmente, un algoritmo si dice *efficiente* se la sua complessità temporale è *polinomiale*.
=== Definizione di classi di complessità
Vogliamo utilizzare il concetto di _classi di equivalenza_ per definire delle classi che racchiudano tutti i problemi che hanno bisogno della stessa quantità di risorse computazionali per essere risolti correttamente.
Una *classe di complessità* è un insieme dei problemi che vengono risolti entro gli stessi limiti di risorse computazionali.
=== Classi di complessità principali
Proviamo a definire alcune classi di complessità in funzione della risorsa tempo.
La prima che introduciamo è la classe $ dtime(f(n)), $ definita come l'insieme dei problemi risolti da una DTM in tempo deterministico $t(n) = O(f(n))$. Sappiamo in realtà che la definizione corretta dovrebbe riguardare i _linguaggi accettati_, ma abbiamo visto nella scorsa lezione che abbiamo una analogia tra essi.
Nella scorsa lezione abbiamo inoltre mostrato che le DTM possono anche calcolare funzioni, quindi possiamo propagare questa definizione di DTIME anche alle funzioni stesse, ovvero possiamo definire delle classi di complessità anche per le funzioni.
_Ma cosa intendiamo con "complessità in tempo per una funzione"?_
La funzione $f : Sigma^* arrow.long Gamma^*$ è calcolata con *complessità in tempo* $t(n)$ dalla DTM $M$ se e solo se su ogni input $x$ di lunghezza $n$ la computazione di $M$ su $x$ si arresta entro $t(n)$ passi, avendo $f(x)$ sul nastro.
Detto ciò, introduciamo la classe $ ftime(f(n)) $ definita come l'insieme delle funzioni risolte da una DTM in tempo deterministico $t(n) = O(f(n))$.
Grazie a quanto detto finora, possiamo definire due classi di complessità storicamente importanti: $ P = union.big_(k gt.eq 0) dtime(n^k) $ *classe dei problemi risolti da una DTM in tempo polinomiale* e $ fp = union.big_(k gt.eq 0) ftime(n^k) $ *classe delle funzioni calcolate da una DTM in tempo polinomiale*.
Questi sono universalmente riconosciuti come i problemi efficientemente risolubili in tempo.
_Ma perché *polinomiale* è sinonimo di efficiente in tempo?_
Possiamo dare tre motivazioni:
- *pratica*: facendo qualche banale esempio, è possibile vedere come la differenza tra un algoritmo polinomiale e uno esponenziale, per input tutto sommato piccoli, è abissale: il tempo di risoluzione di un problema, nel primo caso, è di frazioni di secondo, mentre nel secondo arriva facilmente ad anni o secoli;
- *"composizionale"*: programmi efficienti che richiamano routine efficienti rimangono efficienti, questo perché concatenare algoritmi efficienti non fa altro che generare un tempo pari alla somma delle complessità dei due algoritmi, che rimane polinomiale in quanto efficienti e polinomiali a loro volta;
- *"robustezza"*: le classi $P$ e $fp$ rimangono invariate a prescindere dai molti modelli di calcolo utilizzati per circoscrivere i problemi efficientemente risolti.
Per l'ultimo motivo, infatti, si può dimostrare che $P$ e $fp$ non dipendono dal modello scelto, che sia RAM, WHILE, DTM, eccetera.
=== Esempio
Facciamo vedere quanto influenzano l'esponente della funzione polinomiale e le costanti dei simboli di Landau. Consideriamo una macchina a $4$GHz che esegue un'operazione ogni $ 1 / (4 dot.op 10^9) $ secondi. Fissiamo anche l'input di grandezza $n = 4000$ caratteri.
La seguente tabella mostra i tempi approssimati di alcune funzioni su input di grandezza $n$.
#align(center)[
#table(
columns: (35%, 35%),
inset: 10pt,
align: horizon,
[*Funzione* $t(n)$], [*Tempo di esecuzione*],
[$n$], [$approx mu s$],
[$n^2$], [$approx m s$],
[$n^3$], [$approx s slash a$],
[$2^n$], [$1$ gogol, ovvero $10^100$ secondi, più dell'età dell'universo]
)
]
Infine, parliamo di costanti nei simboli di Landau: con costanti molto grandi riesco a inserire algoritmi inefficienti negli efficienti e viceversa. Ad esempio, l'algoritmo del _quicksort_ è più lento nel _worst case_ dell'algoritmo del _mergesort_, però la costante del mergesort è più grande di quella del quicksort.
== Tesi di Church-Turing estesa
La *tesi di Church-Turing estesa* afferma che la classe dei problemi *efficientemente risolubili in tempo* coincide con la classe dei problemi risolti in _tempo polinomiale_ su DTM.
La possiamo vedere come la _versione quantitativa_ della tesi di Church-Turing.
== Chiusura di $P$
#theorem(numbering: none)[
La classe $P$ è un'algebra di Boole, ovvero è chiusa rispetto alle operazioni di unione, intersezione e complemento.
]
#proof[
#block(
fill: rgb("#9FFFFF"),
inset: 8pt,
radius: 4pt,
[UNIONE]
)
Date due istanze $A,B in P$, siano $M_A$ e $M_B$ due DTM con tempi rispettivamente $p(n)$ e $q(n)$. Allora il seguente programma (_ad alto livello_) $ P equiv & "input"(n) \ & y := M_A (x); \ & z := M_B (x); \ & "output"(y or z) $ permette il calcolo dell'unione di $A$ e $B$ in tempo $t(n) = p(n) + q(n)$.
#block(
fill: rgb("#9FFFFF"),
inset: 8pt,
radius: 4pt,
[INTERSEZIONE]
)
Date due istanze $A,B in P$, siano $M_A$ e $M_B$ due DTM con tempi rispettivamente $p(n)$ e $q(n)$. Allora il seguente programma (_ad alto livello_) $ P equiv & "input"(n) \ & y := M_A (x); \ & z := M_B (x); \ & "output"(y and z) $ permette il calcolo dell'intersezione di $A$ e $B$ in tempo $t(n) = p(n) + q(n)$.
#block(
fill: rgb("#9FFFFF"),
inset: 8pt,
radius: 4pt,
[COMPLEMENTO]
)
Data l'istanza $A in P$, sia $M_A$ una DTM con tempo $p(n)$. Allora il seguente programma (_ad alto livello_) $ P equiv & "input"(n) \ & y := M_A (x); \ & "output"(not y) $ permette il calcolo del complemento di $A$ in tempo $t(n) = p(n)$.
]
La classe $P$, inoltre, è anche chiusa rispetto all'operazione di *composizione*: infatti, posso comporre tra loro le macchine di Turing come se fossero procedure black box. Facendo l'esempio con due DTM, otteniamo $ x arrow.long.squiggly M_1 arrow.long.squiggly x' arrow.long.squiggly M_2 arrow.long.squiggly y. $ Supponiamo che le macchine $M_1$ e $M_2$ abbiano tempo rispettivamente $p(n)$ e $q(n)$, allora il tempo totale è $ t(n) lt.eq p(n) + q(p(n)) . $ Usiamo $q(p(n))$ perché eseguendo $M_1$ in $p(n)$ passi il massimo output che scrivo è grande $p(n)$.
== Problemi difficili
Esistono moltissimi problemi pratici e importanti per i quali ancora non sono stati trovati algoritmi efficienti e non è nemmeno stato provato che tali algoritmi non possano per natura esistere.
In altre parole, non sappiamo se tutti i problemi sono in realtà efficientemente risolubili o se ne esistono alcuni il cui miglior algoritmo di risoluzione abbia una complessità esponenziale.
|
|
https://github.com/typst/packages | https://raw.githubusercontent.com/typst/packages/main/packages/preview/rubby/0.10.0/CHANGELOG.md | markdown | Apache License 2.0 | # Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a
Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to
[Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [Unreleased]
## [0.10.0] - 2023-11-24
### Changed
- Values are now compared with "first-class values" types instead of strings
(see [Typst 0.8.0 release notes](https://github.com/typst/typst/releases/tag/v0.8.0))
(**breaking change**).
### Added
- Added minimal Typst version to `0.8.0` (see the reason above).
## [0.9.2] - 2023-09-14
### Fixed
- Fixed import in example.typ.
## [0.9.1] - 2023-09-14
### Fixed
- Fixed example.typ.
## [0.9.0] - 2023-09-14
### Changed
Now kebab case is used instead of snake case.
- Renamed function `get_ruby` to `get-ruby` (**breaking change**).
- Renamed `get-ruby`'s argument `auto_spacing` to `auto-spacing` (**breaking
change**).
## [0.8.0] - 2023-07-03
Initial release.
[0.10.0]: https://github.com/Andrew15-5/rubby/releases/tag/v0.10.0
[0.9.2]: https://github.com/Andrew15-5/rubby/releases/tag/v0.9.2
[0.9.1]: https://github.com/Andrew15-5/rubby/releases/tag/v0.9.1
[0.9.0]: https://github.com/Andrew15-5/rubby/releases/tag/v0.9.0
[0.8.0]: https://github.com/Andrew15-5/rubby/releases/tag/v0.8.0
|
https://github.com/tingerrr/masters-thesis | https://raw.githubusercontent.com/tingerrr/masters-thesis/main/src/figures/algorithms.typ | typst | #import "util.typ": *
#let comment(body) = text(gray, {
h(1fr)
sym.triangle.r
[ ]
body
})
#let dd = $Delta d$
#let Int = math-type("Int")
#let None = math-type("None")
#let Node = math-type("Node")
#let Deep = math-type("Deep")
#let Key = math-type("Key")
#let Shallow = math-type("Shallow")
#let FingerTree = math-type("FingerTree")
#let popl = math-func("pop-left")
#let pushl = math-func("push-left")
#let popr = math-func("pop-right")
#let pushr = math-func("push-right")
#let concat = math-func("concat")
#let split = math-func("split")
#let last = math-func("last")
#let rev = math-func("rev")
#let btsearch = math-func("btree-search")
#let btsplit = math-func("btree-split")
#let dsearch = math-func("digit-search")
#let dsplit = math-func("digit-split")
#let pnodes = math-func("pack-nodes")
#let ftsearch = math-func("ftree-search")
#let ftpushl = math-func("ftree-push-left")
#let ftpushr = math-func("ftree-push-right")
#let ftpopl = math-func("ftree-pop-left")
#let ftpopr = math-func("ftree-pop-right")
#let ftappendl = math-func("ftree-append-left")
#let fttakel = math-func("ftree-take-left")
#let ftappendr = math-func("ftree-append-right")
#let fttaker = math-func("ftree-take-right")
#let ftsplit = math-func("ftree-split")
#let ftconcat = math-func("ftree-concat")
#let ftinsert = math-func("ftree-insert")
#let ftremove = math-func("ftree-remove")
#let finger-tree-alg-search = algorithm(
numbered-title: $ftsearch(t, m): (FingerTree, Key) -> Node$,
)[
+ *if* $t$ *is* $Shallow$
+ *if* $m <= t."key"$
+ *return* $dsearch(t."digits", m)$
+ *else*
#comment[key not in this subtree]
+ *return* $None$
+ *else*
#comment[find suitable branch to descend]
+ *if* $m <= t."left"."key"$
+ *return* $dsearch(t."left", m)$
+ *else if* $m <= t."middle"."key"$
+ *return* $ftsearch(t."middle", m)$
+ *else if* $m <= t."right"."key"$
+ *return* $dsearch(t."right", m)$
+ *else*
#comment[key not in this subtree]
+ *return* $None$
]
#let finger-tree-alg-push-left = algorithm(
numbered-title: $ftpushl(t, e): (FingerTree, Node) -> FingerTree$,
)[
+ *if* $t$ *is* $Shallow$
#comment[overflow by split into]
+ *let* $"digits" = pushl(t."digits", e)$
+ *if* $abs("digits") <= 2d_min$
#comment[no split]
+ *return* $Shallow("digits")$
+ *else*
+ *let* $"left", "right" := split("digits"."children", d_min)$
+ *return* $Deep("left", None, "right")$
+ *else*
+ *let* $"left" := pushl(t."left"."children", e)$
+ *if* $abs("left") <= d_max$
#comment[no overflow]
+ *return* $Deep("left", t."middle", t."right")$
+ *else*
+ *let* $"rest", "overflow" := split("left", abs("left") - dd)$
#comment[overflow by descent]
+ *let* $"middle" := ftpushl(t."middle", Node("overflow"))$
+ *return* $Deep("rest", "middle", t."right")$
]
#let finger-tree-alg-pop-left = algorithm(
numbered-title: $ftpopl(t): FingerTree -> (Node, FingerTree)$,
)[
+ *if* $t$ *is* $Shallow$
+ *if* $abs(t."digits") = 0$
+ *return* $(None, t)$
+ *else*
+ *let* $e, "rest" := popl(t."digits")$
+ *return* $(e, Shallow("rest"))$
+ *else*
+ *let* $e, "rest"_l := popl(t."left"."digits")$
+ *if* $abs("rest"_l) >= d_min$
#comment[no underflow]
+ *return* $(e, Deep("rest"_l, t."middle", t."right"))$
+ *else if* $abs(t."middle") = 0$
#comment[underflow by left+right merge]
+ *let* $"middle" = concat(t."left", t."right")$
+ *if* $abs("middle") >= 2d_min$
+ *let* $"left", "right" = split("middle", floor(abs("middle") \/ 2))$
+ *return* $(e, Deep("left", Shallow(None), "right"))$
+ *else*
+ *return* $(e, Shallow("middle"))$
+ *else*
#comment[underflow by descent]
+ *let* $"node", "rest"_m := ftpopl(t."middle")$
+ *return* $(e, Deep(concat("rest"_l, "node"."children"), "rest"_m, t."right"))$
]
#let finger-tree-alg-append-left = algorithm(
numbered-title: $ftappendl(t, "nodes"): (FingerTree, [Node]) -> FingerTree$,
)[
+ *for* $e$ *in* $rev("nodes")$
#comment[simply push all values one by one]
+ $t = ftpushl(t, e)$
+ *return* $t$
]
#let finger-tree-alg-take-left = algorithm(
numbered-title: $fttakel(t, "count"): (FingerTree, Int) -> ([Node], FingerTree)$,
)[
+ *let* $n' = nothing$
+ *for* $"__"$ *in* $1.."count"$
+ *if* $abs(t) = 0$
#comment[no more values left]
+ *break*
+ *else*
+ *let* $e, t' = ftpopl(t)$
+ $t = t'$
+ $n' = pushr(n', e)$
+ *return* $t$
]
#let finger-tree-alg-nodes = algorithm(
numbered-title: $pnodes(n) : [Node] -> [Node]$,
)[
+ *if* $abs(n) < k_min$
#comment[can't form a single node]
+ *return* $None$
+ *else*
+ *let* $n' := nothing$
+ *while* $abs(n) - k_max >= k_min$
#comment[push max size nodes as long as it goes]
+ *let* $"children", "rest" = split(n, k_max)$
+ $n = "rest"$
+ $n' = pushr(n', Node("children"))$
+ *if* $abs(n) - k_min >= k_min$
#comment[push the remaining 1 or 2 nodes]
+ *let* $a, b = split(n, k_min)$
+ $n' = pushr(n', Node(a))$
+ $n' = pushr(n', Node(b))$
+ *else*
+ $n' = pushr(n', Node(n))$
+ *return* $n'$
]
#let finger-tree-alg-concat = algorithm(
numbered-title: $ftconcat(l, m, r): (FingerTree, [Node], FingerTree) -> FingerTree$,
)[
+ *if* $l$ *is* $Shallow$
+ *return* $ftappendl(r, pushl(m, l."digits"))$
+ *else if* $r$ *is* $Shallow$
+ *return* $ftappendr(l, pushr(m, r."digits"))$
+ *else*
+ *let* $m' := pnodes(concat(l."right", m, r."left"))$
#comment[pack nodes for the next layer]
+ *return* $Deep(l."left", ftconcat(l."middle", m', r."middle"), r."right")$
]
#let finger-tree-alg-split = algorithm(
numbered-title: $ftsplit(t, k): (FingerTree, Key) -> (FingerTree, Node, FingerTree)$,
)[
+ *if* $t$ *is* $Shallow$
+ *let* $l, v, r := dsplit(t."digits", k)$
+ *return* $(Shallow(l), v, Shallow(r))$
+ *else*
+ *if* $k <= t."left"."key"$
+ *let* $l, v, r := dsplit(t."left"."children", k)$
+ *return* $(Shallow(l), v, Deep(r, t."middle", t."right"))$
+ *else if* $k <= t."middle"."key"$
+ *let* $l, v, r := ftsplit(t."middle", k)$
#comment[descend and unpack]
+ *let* $l', v', r' := dsplit(v."children", k)$
+ *return* $(Deep(t."left", l, l'), v', Deep(r', r, t."right"))$
+ *else if* $k <= t."right"."key"$
+ *let* $l, v, r := dsplit(t."right"."children", k)$
+ *return* $(Deep(t."left", t."middle", l), v, Shallow(r))$
+ *else*
+ *return* $(t, Shallow(nothing))$
]
#let finger-tree-alg-insert = algorithm(
numbered-title: $ftinsert(t, e): (FingerTree, Node) -> FingerTree$,
)[
+ *let* $l, v, r := ftsplit(t, e."key")$
+ *if* $v$ *is* $None$
#comment[$e."key"$ not in $t$]
+ *let* $l' := ftpushr(l, e)$
+ *return* $ftconcat(l', r)$
+ *else*
#comment[$k$ in $t$]
+ *let* $l' := ftpushr(l, v)$
+ *let* $l'' := ftpushr(l', e)$
+ *return* $ftconcat(l'', r)$
]
#let finger-tree-alg-remove = algorithm(
numbered-title: $ftremove(t, k): (FingerTree, Key) -> (FingerTree, Node)$,
)[
+ *let* $l, v, r := ftsplit(t, k)$
+ *if* $v$ *is* $None$
#comment[$k$ not in $t$]
+ *return* $(t, None)$
+ *else*
#comment[$k$ in $t$]
+ *let* $t' := ftconcat(l, r)$
+ *return* $(t', v)$
]
|
|
https://github.com/markcda/unitech-typst | https://raw.githubusercontent.com/markcda/unitech-typst/master/examples/pr-infosec-basics/01-project.typ | typst | MIT License | #import "00-university-template.typ": *
#show: student_work.with(
title: "Проект - Система контроля и управления доступом - Прусак<NAME>., <NAME>.",
header: "unitech-2023-header.png",
department_name: "Кафедра информационной безопасности",
institute_name: "Институт инфокоммуникационных систем и технологий",
work_type: "проект",
discipline_name: "Основы информационной безопасности",
theme: "Система контроля и управления доступом",
author: (name: "<NAME>, <NAME>", sex: "them", degree: "студенты", group: "ИБО-ТС-22", nwa: "Прусакова Ю.А., <NAME>."),
adviser: (name: "<NAME>", sex: "male", degree: "заведующий лабораторией кафедры ИБ", nwa: "Ульянов Д.В."),
city: "Королёв",
year: "2023",
table_of_contents: true,
links: (
//(type: "doc", title: "Доктрина информационной безопасности Российской Федерации (от 5 декабря 2016 г.)"),
//(type: "book", author: "<NAME>", title: "Севейна", publisher: "Литрес.Самиздат", year: "2019"),
//(type: "web", title: "Writing In Typst Tutorial", link: "https://typst.app/docs/tutorial/writing-in-typst", access_date: "22.09.2023"),
),
)
= Введение
В связи с постоянно ускоряющимся научно-техническим прогрессом эволюционируют и угрозы информационной безопасности. Для того, чтобы им противостоять, требуется непрерывно улучшать и модернизировать технические, аппаратные и программные средства защиты информации, совершенствовать политики информационной безопасности предприятия и осуществлять постоянный мониторинг угроз информационной безопасности.
Целью данной работы является совершенствование системы информационной безопасности путём внедрения новой системы контроля и управления доступом на предприятии АО "МашПриборКомплект".
Задачи работы:
1. Доработка Устава проекта.
2. Разработка Спецификаций оборудования и ПО СКУД.
3. Доработка Обобщённого плана реализации проекта и отчётности по нему.
4. Разработка диаграммы Ганта на весь временной промежуток реализации проекта.
#set heading(numbering: "1.")
= Доработка Устава проекта
Ключевой задачей в доработке Устава проекта системы контроля и управления доступом АО "МашПриборКомплект" (далее -- АО "МПК") является предложение по внедрению технических решений защиты информации и разработка этапов реализации проекта.
В соответствии с действующей «Политикой информационной безопасности АО «МПК» сервер СКУД и рабочие места администратора СКУД и Бюро пропусков размещаются в обособленных помещениях *без их подключения* к ИТКС предприятия и сети Интернет. Тем не менее, сервер СКУД, рабочие места администратора СКУД и Бюро пропусков должны быть дополнительно защищены следующими техническими решениями:
1. Модуль доверенной загрузки операционной системы. Этот модуль гарантирует загрузку только с доверенными компонентами.
2. DLP-система. Такая система сможет пресекать попытки хищения личной информации сотрудников, циркулирующей по локальной сети СКУД, и не допускать внешних инъекций.
3. Резервные источники питания. Они будут гарантировать работоспособность системы СКУД в случае аварийных или чрезвычайных ситуаций.
В рамках реализации проекта предлагаются следующие этапы:
1. Подготовительные работы (создание спецификаций для аппаратного и программного обеспечения, разработка схемы размещения зданий и СКУД, завершение отделочных работ и работ по размещению инфраструктурных коммуникаций в новом комплексе).
2. Установка оборудования СКУД и настройка системы контроля доступа.
3. Настройка системы аутентификации и авторизации.
4. Обучение персонала предприятия использованию новой системы.
= Спецификации оборудования и ПО СКУД
Внедрение СКУД является сложным процессом, который требует тщательного отбора оборудования и программного обеспечения, нацеленных на обеспечение безопасности информационных ресурсов. В данном разделе осуществляется анализ спецификаций и мероприятий, предпринимаемых для обеспечения информационной безопасности на предприятии АО "МПК". В этом контексте разрабатывается комплексная СКУД, которая включает в себя аспекты физической безопасности и средства защиты информации, обеспечивая высокий уровень надежности и стабильную работу предприятия.
Предприятие имеет два основных контура:
1. Внутренний контур, который обеспечивает независимую безопасность с использованием аналогового оборудования, такого как аналоговые камеры, установленные в особо охраняемых зонах предприятия.
2. Внешний контур, который обеспечивает связь с внешним миром с использованием сетевых устройств, таких как поворотные сетевые видеокамеры, технология PoE и другие.
Предлагается реализация СКУД на основе идентификации персонала по личным бесконтактным картам–пропускам с последующей автоматической верификацией по 2D-изображению лица. Поскольку до 2024 года возможно увеличение штатной численности до 950 человек, предлагается оснастить контрольно-пропускной пункт минимум тремя турникетами. Также известно, что офисно-административное здание соединено с производственным корпусом; предлагается оснастить переход между корпусами на втором этаже дополнительным контрольно-пропускным пунктом.
#set figure.caption(separator: [. ])
#figure(
text(
size: 8pt,
table(
columns: 3,
inset: 4pt,
align: horizon,
align(center)[*Наименование*], align(center)[*Описание*], align(center)[*Предназначение*],
[АВ Bolid VCG-528], [Камера для видеонаблюдения с возможностью поворота. Позволяет идентифицировать личность человека с расстояния до 16 м], [Визуальный мониторинг и запись событий в области видимости камеры, подходит для различных сценариев видеонаблюдения],
[АВ Bolid VCG-822], [Купольная камера для видеонаблюдения в офисных и общественных помещениях. Позволяет идентифицировать личность человека с расстояния до 4,4 м], [Мониторинг и запись событий в офисных и общественных помещениях с высоким качеством изображения],
[АВШ Hurde Block-A1 4m], [Устройство для контроля движения транспорта на въезде и выезде. Перекрытие проёма шириной до 4 метров], [Ограничение доступа транспортных средств на охраняемую территорию, обеспечение безопасности и контроля проезда],
[ВЗСВ Bolid VCI-123.TK-EX-2A2], [Камера, соответствующая стандартам безопасности и пригодная для эксплуатации в опасных зонах, где возможен риск возгорания или взрыва. Эта камера обеспечивает надежное видеонаблюдение в условиях повышенной опасности], [Оборудование защищено от взрывов и обладает специальными сертификатами безопасности]
)
),
caption: [Внешнее оборудование безопасности]
)
#figure(
text(
size: 8pt,
table(
columns: 3,
inset: 4pt,
align: horizon,
align(center)[*Наименование*], align(center)[*Описание*], align(center)[*Предназначение*],
[МД "ПАУТИНА-А3"], [Устройство, предназначенное для обнаружения металлических предметов на входе в помещение], [Используется для обеспечения безопасности, обнаружения запрещенных металлических предметов и контроля доступа в офисных помещениях и технических зонах],
[ТТ С2000-УТ-111], [Система контроля доступа, позволяющую разрешать или запрещать проход посетителям на основе авторизации], [Используется для контроля доступа персонала и посетителей в офисных помещениях и технических зонах, обеспечивает безопасность и ограничивает доступ],
[СВ Bolid VCI-884], [Устройство для видеонаблюдения и записи в реальном времени в офисных помещениях], [Используется для наблюдения и контроля за событиями в офисных помещениях, обеспечивая безопасность и видеозапись для документации]
)
),
caption: [Внутреннее оборудование безопасности - Офисное помещение]
)
#figure(
text(
size: 8pt,
table(
columns: 3,
inset: 4pt,
align: horizon,
align(center)[*Наименование*], align(center)[*Описание*], align(center)[*Предназначение*],
[МД "ПАУТИНА-А3"], [Устройство, предназначенное для обнаружения металлических предметов на входе в помещение], [Используется для обеспечения безопасности, обнаружения запрещенных металлических предметов и контроля доступа в офисных помещениях и технических зонах],
[ТТ С2000-УТ-111], [Система контроля доступа, позволяющую разрешать или запрещать проход посетителям на основе авторизации], [Используется для контроля доступа персонала и посетителей в офисных помещениях и технических зонах, обеспечивает безопасность и ограничивает доступ],
[АВ Bolid VCG-528], [Камера для видеонаблюдения и записи видео в технических помещениях], [Визуальный мониторинг и запись событий в области видимости камеры, подходит для различных сценариев видеонаблюдения],
[АВ Bolid VCG-220], [Камера для видеонаблюдения и записи видео в технических помещениях], [Визуальный мониторинг и запись событий в области видимости камеры, подходит для различных сценариев видеонаблюдения],
[БКД C2000-BIOACCESS-SF10], [Система контроля доступа на основе биометрических данных], [Используется для обеспечения высокой безопасности и авторизации сотрудников и посетителей в технических зонах и офисных помещениях]
)
),
caption: [Внутреннее оборудование безопасности - Технические помещения]
)
#figure(
text(
size: 8pt,
table(
columns: 3,
inset: 4pt,
align: horizon,
align(center)[*Наименование*], align(center)[*Описание*], align(center)[*Предназначение*],
[ВА высокого разрешения Bolid RGG-0412], [Оборудование для записи и хранения видеосигнала высокого разрешения с аналоговых камер], [Используется для записи видео с аналоговых камер, обеспечивая хранение и воспроизведение высококачественных записей],
[ДС вс-25-12-1-1], [Оборудование для преобразования аналогового видеосигнала в цифровой и его передачи по сети], [Используется для интеграции аналоговых видеокамер в сеть, обеспечивая удаленный мониторинг и запись видео],
[РС "Эльбрус 801-РС" (ТВГИ.466535.175)], [Рабочая станция на базе микропроцессора Эльбрус-8С], [Предназначена для автоматизированных рабочих мест (АРМ) операторов, микросерверов и информационных терминалов, средств промышленной автоматизации и систем с повышенными требованиями к информационной безопасности],
[АПМДЗ "Соболь"], [Сертифицированный аппаратно-программный модуль доверенной загрузки], [Используется для контроля целостности системного реестра Windows, аппаратной конфигурации компьютера и файлов до загрузки],
[Zecurion DLP 11], [Гибридная DLP-система], [Используется для защиты от утечек данных],
[ВК "Эльбрус-8.32" (твги.466535.164)], [Высокопроизводительный сервер, предназначенный для обработки и хранения данных], [Используется для выполнения вычислительных задач, обработки данных и хранения информации на высоком уровне производительности],
[РИП-48 исп.01 (рип-48–4/17м3-р-rs)], [Оборудование для обеспечения надежного электропитания систем видеонаблюдения и контроля доступа], [Используется для обеспечения непрерывного электропитания и безопасности объектов],
[СК Bolid SW-224], [Устройство для управления и распределения сетевого трафика], [соединения и управления сетевыми устройствами, обеспечивая передачу данных между ними и управление сетевым трафиком],
[Стойка 19" двухрамная 47u, 600x1000мм (универсальная)], [Двухрамная стойка 19" предназначена для установки оборудования в стандартных 19-дюймовых шкафах], [Используется для монтажа и организации пространства в стойках 19", обеспечивая надежную фиксацию и размещение оборудования],
[Шкаф 19" настенный 6u (600x300) дверь, стекло], [Шкаф для монтажа оборудования и его защиты в офисных и технических помещениях], [Используется для установки и защиты оборудования в ограниченных пространствах, обеспечивая компактное и надежное размещение]
)
),
caption: [Сервер СКУД (центр обработки данных)]
)
= Обобщённый план реализации проекта
Для реализации проекта требуется поочерёдно выполнить следующие работы:
1. Подготовить, согласовать и подписать сторонами спецификации на комплект оборудования и ПО СКУД; правил и прав доступа на объект -- по каждому корпусу, выделенным зонам и помещениям применительно к сотрудникам предприятия и посетителям; ТЗ и договора на проведение работ и оказание услуг.
2. Закупить оборудование и программное обеспечение.
3. Создать и актуализировать базу фотографий и установочных данных всего персонала предприятия.
4. Принять выполненные работы по слаботочным сетям.
5. Произвести монтаж оборудования СКУД на входной зоне и сервере.
6. Произвести монтаж оборудования СКУД в офисных и технических помещениях.
7. Установить и настроить программное обеспечение.
8. Подготовить и согласовать ПМИ и проведение приемо–сдаточных испытаний СКУД.
9. Утвердить протоколы испытаний, подписать акты выполненных работ, выставить счета к оплате.
10. Сдать СКУД в промышленную эксплуатацию.
|
https://github.com/noahjutz/CV | https://raw.githubusercontent.com/noahjutz/CV/main/sidebar/main.typ | typst | #import "section.typ": section
#import "social.typ": social
#import "langskill.typ": langskill
#import "/chip.typ": chips
#import "/env.typ"
#box(radius: 16pt, clip: true)[
#image("/assets/profile_small.JPG")
]
#section("Kontakt")
#social(al: top,
"/assets/icons/location.svg",
env.address
)
#social(
"/assets/icons/call.svg",
url: "tel:" + env.phone,
env.phone
)
#social(
"/assets/icons/mail.svg",
url: "mailto:" + env.email,
env.email
)
#social(
"/assets/brands/github.svg",
url: "https://github.com/noahjutz",
"noahjutz"
)
#v(16pt)
#section("Sprachkenntnisse")
#langskill("Deutsch", "C2")
#langskill("Englisch", "C2")
#langskill("Spanisch", "B1")
#langskill("Arabisch", "A2")
#v(16pt)
#section("Andere Kenntnisse")
#chips(
"Kotlin",
"Python",
"Linux",
"Git",
"Java",
"C",
"JavaScript",
"PostScript",
"Svelte",
"Postgres",
"MongoDB",
"LaTeX",
) |
|
https://github.com/Myriad-Dreamin/shiroa | https://raw.githubusercontent.com/Myriad-Dreamin/shiroa/main/README.md | markdown | Apache License 2.0 | # shiroa
[_shiroa_](https://github.com/Myriad-Dreamin/shiroa) (_Shiro A_, or _The White_, or _云笺_) is a simple tool for creating modern online (cloud) books in pure typst.
## Installation (shiroa CLI)
There are multiple ways to install the [shiroa](https://github.com/Myriad-Dreamin/shiroa) CLI tool.
Choose any one of the methods below that best suit your needs.
### Pre-compiled binaries
Executable binaries are available for download on the [GitHub Releases page](https://github.com/Myriad-Dreamin/shiroa/releases).
Download the binary for your platform (Windows, macOS, or Linux) and extract the archive.
The archive contains an `shiroa` executable which you can run to build your books.
To make it easier to run, put the path to the binary into your `PATH`.
### Build from source using Rust
To build the `shiroa` executable from source, you will first need to install Yarn, Rust, and Cargo.
Follow the instructions on the [Yarn installation page](https://classic.yarnpkg.com/en/docs/install) and [Rust installation page](https://www.rust-lang.org/tools/install).
shiroa currently requires at least Rust version 1.75.
To build with precompiled artifacts, run the following commands:
```sh
cargo install --git https://github.com/Myriad-Dreamin/shiroa --locked shiroa-cli
```
To build from source, run the following commands:
```sh
git clone https://github.com/Myriad-Dreamin/shiroa.git
git submodule update --recursive --init
cargo run --bin shiroa-build
# optional: install it globally
cargo install --path ./cli
```
With global installation, to uninstall, run the command `cargo uninstall shiroa`.
Again, make sure to add the Cargo bin directory to your `PATH`.
### Get started
See the [Get-started](https://myriad-dreamin.github.io/shiroa/guide/get-started.html) online documentation.
### Setup for writing your book
We don't provide a watch command, but `shiroa` is designated to embracing all of the approaches to writing typst documents. It's feasible to preview your documents by following approaches (like previewing normal documents):
- via [Official Web App](https://typst.app).
- via VSCod(e,ium), see [Tinymist](https://marketplace.visualstudio.com/items?itemName=myriad-dreamin.tinymist) and [Typst Preview](https://marketplace.visualstudio.com/items?itemName=mgt19937.typst-preview).
- via other editors. For example of neovim, see [typst.vim](https://github.com/kaarmu/typst.vim) and [Typst Preview](https://github.com/Enter-tainer/typst-preview#use-without-vscode).
- via `typst-cli watch`, See [typst-cli watch](https://github.com/typst/typst#usage).
### Acknowledgement
- The [mdbook theme](./themes/mdbook/) is borrowed from [mdBook](https://github.com/rust-lang/mdBook/tree/master/src/theme) project.
- Compile the document with awesome [Typst](https://github.com/typst/typst).
|
https://github.com/typst/packages | https://raw.githubusercontent.com/typst/packages/main/packages/preview/tlacuache-thesis-fc-unam/0.1.1/lib.typ | typst | Apache License 2.0 |
#let bib = state("bib", none)
#let currentH(level: 1)={
let elems = query(selector(heading.where(level: level)).after(here()))
if elems.len() != 0 and elems.first().location().page() == here().page() {
return elems.first().body
} else {
elems = query(selector(heading.where(level: level)).before(here()))
if elems.len() != 0 {
return elems.last().body
}
}
return ""
}
#let thesis(
titulo: [Titulo],
grado: [Licenciatura],
autor: [Autor],
asesor: [Asesor],
lugar: [Ciudad de México, México],
agno: [#datetime.today().year()],
bibliography: [],
body,
)={
// configuración páginas y contadores
set document(title: titulo)
set page("us-letter", margin: (top: 4cm, bottom: 2cm), header: context{
if here().page() == 1 {
return
}
if calc.rem(here().page(), 2) == 0 [
#align(left, text(currentH(), size: 18pt))
#line(length: 100%, start: (0%, -7%))
] else [
#align(right, currentH(level: 2))
#line(length: 100%)
]
})
set text(font: "New Computer Modern", lang: "es")
set heading(numbering: "1.1.")
set math.equation(
numbering: num =>
"(" + (counter(heading.where(level: 1)).get() + (num,)).map(str).join(".") + ")",
)
set par(first-line-indent: 1em)
set block(spacing: 1.5em)
// Portada
place(line(length: 70%, start: (30%, 10%), stroke: 3pt))
place(line(length: 70%, start: (30%, 13%)))
place(line(length: 60%, start: (10%, 20%), angle: 90deg, stroke: 3pt))
place(line(length: 60%, start: (13%, 20%), angle: 90deg))
place(image("./escudos/UNAM_crest_black.svg", width: 100pt))
place(bottom, image("./escudos/FC_crest_black.svg", width: 100pt))
set align(center)
move(dx: 70pt, [
#v(1.2cm)
#text(1.5em, [Universidad Nacional Autónoma de México])
#v(1.2cm)
#text(1.5em, [Facultad de Ciencias])
#v(2cm)
#text(1.5em, [#titulo])
#v(2cm)
#text(3em, spacing: 200%, [T e s i s])
#upper([QUE PARA OPTAR POR EL GRADO DE:])
#grado
#v(1cm)
#upper([Presenta])
#autor
#v(1cm)
#upper([DIRECTOR DE TESIS:])
#asesor
#v(1cm)
#lugar, #agno.
])
pagebreak()
// Table of contents.
outline(depth: 3, indent: true)
set page(numbering: "1")
counter(page).update(1)
let line-spacing = 0.65em * 1.5
set par(justify: true, leading: line-spacing)
show heading.where(level: 1): it => [
#pagebreak(to: "even")
#set align(right)
#v(40%)
#set text(font: "Inria Serif", size: 40pt)
#it.body
#line(length: 100%, start: (0%, 0%), stroke: gray)
#pagebreak(weak: true)
]
set align(left)
body
if not bibliography == [] {
[#bibliography <bib>]
}
}
#let chapter(bibliography: [], body) = {
set math.equation(
numbering: num =>
"(" + (counter(heading.where(level: 1)).get() + (num,)).map(str).join(".") + ")",
)
body
context(if query(<bib>).len() != 1 and bibliography == [] {
pagebreak()
bibliography
})
}
#let section(bibliography: [], body) = {
set math.equation(
numbering: num =>
"(" + (counter(heading.where(level: 1)).get() + (num,)).map(str).join(".") + ")",
)
body
context(if query(<bib>).len() != 1 and bibliography == [] {
pagebreak()
bibliography
})
}
|
https://github.com/jomaway/typst-teacher-templates | https://raw.githubusercontent.com/jomaway/typst-teacher-templates/main/ttt-lists/template/students.typ | typst | MIT License | #import "@preview/ttt-lists:0.1.0": studentlist as list
#set page("a4", margin: 1cm)
#set text(14pt, font:"Rubik", weight: 300, lang: "de")
= Class list
#let data = csv("students.csv")
#{ data = list.add_check_column(data, title: "Attending") }
#list.studentlist(
numbered: true,
lines: true,
tag: "Year 24/25",
data,
);
|
https://github.com/MattiaOldani/Informatica-Teorica | https://raw.githubusercontent.com/MattiaOldani/Informatica-Teorica/master/capitoli/complessità/14_dtm.typ | typst | #import "@preview/algo:0.3.3": algo, i, d, code
#import "../alias.typ": *
= Macchina di Turing deterministica (DTM)
Il punto di partenza dello studio della teoria della complessità è la definizione rigorosa delle risorse di calcolo e di come possono essere misurate.
Il modello di calcolo che useremo nel nostro studio è la *Macchina di Turing*, ideata da <NAME> nel 1936. Essa è un modello *teorico* di calcolatore che consente di definire rigorosamente:
- i passi di computazione e la computazione stessa;
- tempo e spazio di calcolo dei programmi;
== Struttura
Una *macchina di Turing deterministica* è un dispositivo hardware fornito di:
- *nastro di lettura e scrittura*: nastro infinito formato da celle, ognuna delle quali ha un proprio indice/indirizzo e contiene un simbolo. Questo nastro viene usato come _contenitore_ per l'input, ma anche come memoria durante l'esecuzione;
- *testina di lettura e scrittura two-way*: dispositivo che permette di leggere e scrivere dei simboli sul nastro ad ogni passo;
- *controllo a stati finiti*: automa a stati finiti $Q = {Q_0, dots, Q_n}$ che permette di far evolvere la computazione.
Un passo di calcolo è una *mossa* che, dato lo stato corrente e il simbolo letto dalla testina, porta la DTM in un nuovo stato, scrivendo eventualmente un simbolo sul nastro e spostando eventualmente la testina. I risultati della mossa, quindi il nuovo stato, il simbolo da scrivere e il movimento della testina vengono calcolati tramite una *funzione di transizione*, basata sui due input dati.
=== Definizione informale
Il funzionamento di una DTM $M$ su input $x in Sigma^*$ passa per due fasi:
+ *inizializzazione*:
- la stringa $x$ viene posta, simbolo dopo simbolo, nelle celle del nastro dalla cella $1$ fino alla cella $|x|$. Le celle dopo quelle che contengono $x$ contengono il simbolo _blank_;
- la testina si posiziona sulla prima cella;
- il controllo a stati finiti è posto nello stato iniziale;
+ *computazione*:\
- sequenza di mosse dettata dalla funzione di transizione.
La computazione può andare in loop o arrestarsi se raggiunge una situazione in cui non è definita nessuna mossa per lo stato attuale. Diciamo che $M$ accetta $x in Sigma^*$ se $M$ si arresta in uno stato tra quelli finali/accettanti, altrimenti la rifiuta.
Definiamo $L_M = {x in Sigma^* bar.v M "accetta" x}$ il *linguaggio accettato* da $M$.
=== Definizione formale
Una macchina di turing deterministica è una tupla $M = (Q, Sigma, Gamma, delta, q_0, F)$, con:
- $Q$: insieme finito di *stati* assumibili dal controllo a stati finiti;
- $q_0 in Q$: *stato iniziale* da cui partono le computazioni di $M$;
- $F subset.eq Q$: insieme degli *stati finali/accettanti* ove $M$ si arresta accettando l'input;
- $Sigma$: *alfabeto di input* su cui sono definite le stringhe di input;
- $Gamma$: *alfabeto di lavoro* che contiene i simboli che possono essere letti/scritti dal/sul nostro nastro. Vale $Sigma subset Gamma$ perché $Gamma$ contiene il simbolo _blank_;
- $delta : Q times Gamma arrow.long Q times (Gamma slash {"blank"}) times {-1,0,+1}$: *funzione di transizione* che definisce le mosse. È una _funzione parziale_: quando non è definita la macchina si arresta. Inoltre, $M$ non può scrivere il simbolo _blank_, lo può solo leggere.
Analizziamo nel dettaglio lo sviluppo di una DTM $M$ su input $x in Sigma^*$, visto solo informalmente:
- *inizializzazione*:
- il nastro contiene la stringa $x = x_1 dots x_n$;
- la testina è posizionata sul carattere $x_1$;
- il controllo a stati finiti parte dallo stato $q_0$;
- *computazione*: sequenza di mosse definite dalla funzione di transizione $delta$ che manda, ad ogni passo, da $(q_i,gamma_i)$ a $(q_(i+1), gamma_(i+1), {-1,0,+1})$.
Se $delta(q,gamma) = bot$, la macchina $M$ si _arresta_. Quando la testina rimbalza tra due celle o rimane fissa in una sola, si verifica un _loop_. La macchina $M$ accetta $x in Sigma^*$ se e solo la computazione si arresta in uno stato $q in F$.
Come prima, $L_M = {x in Sigma^* bar.v M "accetta" x}$ è ancora il *linguaggio accettato* da $M$.
Queste macchine sono molto simili agli *automi a stati finiti*, seppur con alcune differenze:
- le FSM di default non possono tornare indietro, non sono two-way, ma questa differenza non aumenta la potenza computazionale, serve solo per avere automi più succinti;
- le FSM hanno il nastro a sola lettura, mentre le DTM possono alterare il nastro a disposizione.
=== Configurazione di una DTM
Come per le macchine RAM, proviamo a dare l'idea di *configurazione* delle DTM. Anche qui, possiamo vederla come una foto che descrive completamente $M$ in un certo istante. Questa definizione ci permette di descrivere la computazione come una serie di configurazioni/foto.
Ciò che ci serve ricordare è:
- in che stato siamo;
- in che posizione si trova la testina;
- il contenuto non-blank del nastro.
Definiamo quindi $C = (q,k,w)$ una configurazione con:
- $q$: stato del controllo a stati finiti;
- $k in NN^+$: posizione della testina del nastro;
- $w in Gamma^*$: contenuto non-blank del nastro.
All'inizio della computazione abbiamo la *configurazione iniziale* $C_0 = (q_0, 1, x)$.
Diciamo che una configurazione $C$ è *accettante* se $C = (q in F, k, w)$ ed è *d'arresto* se $C = (q, k, w)$ con $delta(q,w) = bot$.
=== Definizione computazione tramite configurazioni
La computazione di $M$ su $x in Sigma^*$ è la sequenza $ C_0 arrow.long^delta C_1 arrow.long^delta dots.c arrow.long^delta C_(i) arrow.long^delta C_(i+1) arrow.long^delta dots.c , $ dove, $forall i gt.eq 0$, vale che da $C_i$ si passa a $C_(i+1)$ grazie alla funzione $delta$.
La macchina $M$ accetta $x in Sigma^*$ se e solo se $C_0 arrow.long^* C_f$, con $C_f$ configurazione d'arresto e accettante.
Il linguaggio accettato da $M$ ha la stessa definizione data prima.
== Altre versioni delle macchine di Turing
=== Versioni alternative
Il fatto che la macchina sia _deterministica_ implica che, data una configurazione $C_i$, quella successiva è univocamente determinata dalla funzione $delta$. Quindi, data una configurazione $C_i$, esiste una sola configurazione $C_(i+1)$ successiva, a meno di arresti.
Nelle *macchine di Turing non deterministiche* NDTM, data una configurazione $C_i$, può non essere unica la configurazione successiva, quindi non è determinata univocamente.
Nelle *macchine di Turing probabilistiche* PTM, data una configurazione $C_i$, possono esistere più configurazioni nelle quali possiamo entriamo, ognuna associata a una probabilità $p_i in [0,1]$.
Infine, nelle *macchine di Turing quantistiche* QTM, data una configurazione $C_i$, esistono una serie di configurazioni successive nelle quali possiamo entrare osservando le ampiezze delle transizioni $alpha_i$. Queste ampiezze sono numeri complessi in $CC$ tali che:
- $|alpha_i| lt.eq 1$;
- hanno probabilità $|alpha_i|^2$;
- le probabilità sommano a $1$.
=== Versione semplificata
Esibire, progettare e comprendere una DTM è difficile anche in casi molto semplici, perché dobbiamo dettagliare stati, alfabeti, transizioni, eccetera. Solitamente, nel descrivere una DTM, si utilizza uno _pseudocodice_ che ne chiarisce la dinamica.
Esistono una serie di teoremi che dimostrano che qualsiasi frammento di programma strutturato può essere tradotto in una DTM formale e viceversa.
=== Esempio: parità
- Nome: parità.
- Istanza: $x in NN$.
- Domanda: $x$ è pari?
Come codifica utilizziamo quella _binaria_, ovvero $ cod : NN arrow.long {0,1}^* . $ Di conseguenza, il linguaggio da riconoscere è $ L_"PARI" = {x in {0,1}^* bar.v x_1 = 1 and x_(|x|) = 0} union {0}. $
Risolvere il problema _parità_ significa trovare una DTM $M$ che sia un algoritmo deterministico che riconosce proprio $L_"PARI"$.
Ricordando che $M = (Q, Sigma, Gamma, delta, q_0, F)$, la seguente macchina riconosce $L_"PARI"$:
- $Q = {p, z_1, mu, z, r}$ insieme degli stati;
- $Sigma = {0, 1}$ alfabeto;
- $Gamma = {0, 1, blank}$ alfabeto di lavoro;
- $q_0 = p$ stato iniziale;
- $F = {z_1, z}$ insiemi degli stati finali;
- $delta : Q times Gamma arrow.long Q times Sigma times {-1, 0, 1}$ funzione di transizione così definita:
#align(center)[
#table(
columns: (25%, 25%, 25%, 25%),
inset: 10pt,
align: horizon,
[$delta$], [$blank$], [$0$], [$1$],
[$p$], [$bot$], [$(z_1, 0, +1)$], [$(mu, 1, +1)$],
[$z_1$], [$bot$], [$(r, 0, +1)$], [$(mu, 1, +1)$],
[$mu$], [$bot$], [$(z, 0, +1)$], [$(mu, 1, +1)$],
[$z$], [$bot$], [$(z, 0, +1)$], [$(mu, 1, +1)$],
[$r$], [$bot$], [$bot$], [$bot$],
)
]
Notiamo come, anche per un problema così semplice, abbiamo una funzione di transizione abbastanza complicata. Andiamo quindi a utilizzare uno pseudocodice:
#algo(
title: "Parità",
parameters: ("n",)
)[
i := 1; \
f := false; \
switch(x[i]) { #i \
case 0: #i \
i++; \
f := (x[i] == blank); \
break; #d \
case 1: #i \
do { #i \
f := (x[i] == 0); \
i++; #d \
} while (x[i] != blank); #d #d \
} \
return f;
]
Alla fine della sua esecuzione avremo:
- se $x in L_"PARI"$ allora #text(green)[True] ;
- se $x in.not L_"PARI"$ allora #text(red)[False] .
|
|
https://github.com/crd2333/crd2333.github.io | https://raw.githubusercontent.com/crd2333/crd2333.github.io/main/src/docs/Reading/跟李沐学AI（论文）/MAE.typ | typst | // ---
// order: 9
// ---
#import "/src/components/TypstTemplate/lib.typ": *
#show: project.with(
title: "d2l_paper",
lang: "zh",
)
= Masked Autoencoders Are Scalable Vision Learners
- 时间：2021.11
== 标题 & 摘要 & 引言 & 相关工作
- 标题：Masked Autoencoders Are Scalable Vision Learners
- 与之前读的文章的关系
- Transformer：纯基于注意力机制的编码器和解码器，在机器翻译任务上，它比基于RNN的架构要更好一些
- BERT：使用一个 Transformer encoder，拓展到了更一般的 NLP 任务上。使用完形填空的*自监督*的训练机制，这样就不需要使用标号，而是通过预测一个句子里面哪些词不见了，从而获取对文本特征抽取的能力。BERT 极大地扩展了 Transformer 的应用，可以在一个大规模无标号的数据上训练出非常好的模型
- ViT：将 Transformer 用到 CV 上，将整个图片分割成很多个 $16*16$ 的 patch，放进 Transformer 进行训练。ViT 这篇文章证明：假设训练数据足够大，相对于 CNN 的架构来说，ransformer 架构上限可能高一点
- MAE：可以认为是 BERT 的 CV 版。基于 ViT 这篇文章，把整个训练拓展到没有标号的数据上面，通过完形填空来获取对于图片的理解。MAE 并不是第一个将 BERT 拓展到 CV 上的工作，但是很有可能是这一系列工作之中影响力最大的一篇
- 标题中 Auto 表示标号和样本来自同一个东西，在语言领域基本都是 auto，但是在 CV 领域比较难做到 auto，一般是另外标注的内容
- 论文技巧：
+ 在写论文的时候假设算法特别快的话，就写 efficient，假设做的东西比较大，就叫 scalable，二选一来使得文章更有 B 格
+ 标题是一句浓缩后的结论（“什么是一个好同志”），非常强有力的句式，比较客观适合当标题
- CV 和 NLP 领域 Masked Autoencoder 不同的原因
+ CNN里的卷积窗口不太好做掩码，因为在 NLP 里面一个 mask 是一个特定的词，但在 CV 里就是（某个像素）转化成一个值，卷积窗口不好识别；而且也不好加入位置信息（但是卷积其实自带位置信息）。不过现在随着 ViT 的出现这些都不是问题了
+ 两者的信息密度不同。语言高度语义化，但图片中有很多冗余甚至可以通过插值还原，解决方法为高比例掩码，迫使模型学习到更有用的信息
+ 解码器的职责不同。在 NLP 中 decoder 只要一个全连接层就可以了，但是 CV 中就比较困难（在 NLP 中，需要还原到词，相对来说在语义层面上比较高一点；而在 CV 中，需要还原到输入也就是原始像素，相对来说是一个比较低层次的表示）
- 相关工作
+ masked language model，BERT and GPT
+ autoencoding in CV，MAE 也是一种形式上的带去噪的自编码，但跟 GAE 还是很不一样的
+ masked image in encoder，比如 iGPT, BEiT
+ self-supervised learning，之前比较火的是 contrastive learning 和数据增强，autoencoder 是另一种路线
- 提了几个比较大的话题，但没有展开去讲到底有何不同。写作上的建议，最好还是明明白白写出来不要让人去猜
== 方法
- 两个核心的设计
+ 非对称的 encoder-decoder 架构
- 虽然是一个 Autoencoder 架构，但实际上任何模型都有一个 encoder 和一个 decoder。比如说在 BERT（虽然号称 encoder-only） 中的 decoder 就是最后一个全连接输出层，因为 BERT 预测的东西相对来讲比较简单，所以一个简单的全连接层足矣；但是 CV 中相对复杂，因为需要预测一个 patch 中的所有像素
- encoder 只作用在可见的 patch 中，对 encoder 这样巨大的模块来说，节省计算成本
- decoder 比较轻量，能够重构原始的图片
+ 如果只是遮住几块的话，进行插值足矣，模型可能学不到特别的东西；而如果遮住大量的块（比如说把 $75%$ 的块全部遮住），则会得到一个非显然的而且有意义的自监督任务，迫使模型去学习一些更好的特征
- 具体实现
+ Masking：随机采样一些块进行保留，剩下的盖住
+ MAE encoder：用 ViT 的 encoder，把每个可见块拿出来线性投影，加上位置信息
+ MAE decoder：会看到两部分信息：一是变成潜表示的可见块，二是同一向量表示的可学习掩码块，都加上位置信息，送入 Transformer decoder 里。decoder 只在预训练时使用，把它恢复成原始图片
+ Reconstruct target：全连接层输出到 $256$ 维，reshape 成 $16*16$。损失函数为 MSE，只在掩码块上做。然后还提到 normalization 的一个小优化
+ Simple implementation：首先我们通过线性投影和位置编码得到一系列 patch 的 tokens，然后 random shuffle 一下，取出前(e.g.)$25%$ 送入 encoder，用可学习的 mask token 把结果 append 到同样长度，再 unshuffle 回去，加上位置编码并送入 decoder，之后再 reconstruct targets。整个过程避免了稀疏操作非常高效
#fig("/public/assets/Reading/limu_paper/MAE/2024-09-29-14-55-07.png")
= 实验 & 结论
- 先在 ImageNet-1K（100万张图片）上自监督预训练，然后再应用到下游任务（不用 decoder 复原而是拿去分类）进行有监督地微调(fune-tuning or linear probing)
- Baseline 是 ViT-large + 各种新 technique 使得在小数据集上也奏效的版本（甚至精度更高，从 $72.5%$ 提升到了 $82.5%$）。然后如果先使用 MAE 做预训练，然后再在ImageNet-1K 上做微调，提升到了 $84.9%$
- 各种 ablation study
+ decoder 的深度（辅以 fune-tuning or linear probing）
+ decoder 的宽度，$512$ 比较好
+ 在 encoder 中要不要加入被盖住的那些块，不加比较好
+ 重构时候的目标：简单版本、*正则化版本*、PCA 版本、dVAE 版本（像 BERT 一样做预测）
+ 数据增强：MAE 对 data augmentation 不那么敏感
+ 采样方法：最简单的随机最好
- 然后还有 掩码率、训练时间、掩码采样策略、预训练的轮数(fune-tuning or linear probing)、不同的超参数 等等图片
- 评论：MAE 的算法还是非常简单的，就是利用 ViT 来做和 BERT 一样的自监督学习，ViT 已经做了类似的事情了，但是本文在此基础之上提出了几点
+ 需要盖住更多的块，使得剩下的那些块，块与块之间的冗余度没有那么高，这样整个任务就变得复杂一点
+ 使用一个 Transformer 架构的解码器，直接还原原始的像素信息，使得整个流程更加简单一点
+ 加上 ViT 工作之后的各种技术，使得它的训练更加鲁棒一点
|
|
https://github.com/Area-53-Robotics/53B-Notebook-Over-Under-2023-2024 | https://raw.githubusercontent.com/Area-53-Robotics/53B-Notebook-Over-Under-2023-2024/master/entries/pre_building/name_reveal.typ | typst | Creative Commons Attribution Share Alike 4.0 International | #import "/templates/entries.typ": *
#import "/templates/headers.typ": *
#import "/templates/text.typ": *
#create_default_entry(
title: [Name Reveal: Over Under],
date: [April 22nd, 2023],
design: [],
witness: [],
content:[
#box_header(
title: [Gabriel],
color: blue.lighten(60%)
) \
#entry_text()
When the game, “Over Under”, was first announced I thought that it would follow Vex’s usual cycle of games, meaning that the game will involve stacking. However, now I think that the robot will have to do more with moving through obstacles efficiently.
#box_header(
title: [Deb],
color: purple.lighten(60%)
) \
#entry_text()
Given the name of the game, I think this game would involve stacking of some form. I think we will have to stack things over others, and maybe have to put objects under platforms. I think the game objects will have cubes, similar to the ones from Tower Takeover.
#box_header(
title: [Jin],
color: yellow.lighten(60%)
) \
#entry_text()
Considering that we haven't had a stacking game since Tower Takeover, I predict that we will be getting some sort of a stacking game. I think we need to construct a bot that will stack things over a hill like a King of the Hill. Lastly, the bot needs to park under something.
#box_header(
title: [Immad],
color: red.lighten(60%)
) \
#entry_text()
When I heard ”Over Under” I guessed that we would have to either maneuver over obstacles or move game objects under and over a bar. I thought we would have to focus on the size of the robot because there would probably be a lot of obstacles.
#box_header(
title: [Juan],
color: green.lighten(60%)
) \
#entry_text()
When I heard the name “Over Under” I thought of a game involving moving blocks. I believe that this season will result in a game where we have to move our bot over obstacles. We might also need to move objects into slots.
]
) |
https://github.com/kdog3682/2024-typst | https://raw.githubusercontent.com/kdog3682/2024-typst/main/src/ex-multiple-choice-item.typ | typst | #set page(margin: 1in)
#set text(size: 12pt)
#let holder(..items) = {
enum(..items)
}
#{
let num = 1
let a = lorem(60)
let b = block({
let letters = "ABCD"
set enum(numbering: (it) => {
letters.at(it - 1)
}, spacing: 20pt, tight: false, body-indent: 10pt)
enum(
rect(lorem(30)),
rect(lorem(30)),
rect(lorem(30)),
)
})
let val = block(fill: yellow, grid(column-gutter: 20pt, columns: (170pt, 1fr), a, b))
set enum(full: false, numbering: (x) => {
text(weight: "bold", str(x) + ".")
})
holder(val, val)
}
|
|
https://github.com/jgm/typst-hs | https://raw.githubusercontent.com/jgm/typst-hs/main/test/typ/layout/list-03.typ | typst | Other | - Top-level indent
- is fine.
|
https://github.com/Myriad-Dreamin/typst.ts | https://raw.githubusercontent.com/Myriad-Dreamin/typst.ts/main/fuzzers/corpora/visualize/pattern-text_00.typ | typst | Apache License 2.0 |
#import "/contrib/templates/std-tests/preset.typ": *
#show: test-page
// You shouldn't be able to see the text, if you can then
// that means that the transform matrices are not being
// applied to the text correctly.
#let pat = pattern(
size: (30pt, 30pt),
relative: "parent",
square(size: 30pt, fill: gradient.conic(..color.map.rainbow))
);
#set page(
width: 140pt,
height: 140pt,
fill: pat
)
#rotate(45deg, scale(x: 50%, y: 70%, rect(
width: 100%,
height: 100%,
stroke: 1pt,
)[
#lorem(10)
#set text(fill: pat)
#lorem(10)
]))
|
https://github.com/TypstApp-team/typst | https://raw.githubusercontent.com/TypstApp-team/typst/master/tests/typ/text/font.typ | typst | Apache License 2.0 | // Test configuring font properties.
---
// Set same font size in three different ways.
#text(20pt)[A]
#text(2em)[A]
#text(size: 15pt + 0.5em)[A]
// Do nothing.
#text()[Normal]
// Set style (is available).
#text(style: "italic")[Italic]
// Set weight (is available).
#text(weight: "bold")[Bold]
// Set stretch (not available, matching closest).
#text(stretch: 50%)[Condensed]
// Set font family.
#text(font: "IBM Plex Serif")[Serif]
// Emoji.
Emoji: 🐪, 🌋, 🏞
// Colors.
#[
#set text(fill: eastern)
This is #text(rgb("FA644B"))[way more] colorful.
]
// Disable font fallback beyond the user-specified list.
// Without disabling, New Computer Modern Math would come to the rescue.
#set text(font: ("PT Sans", "Twitter Color Emoji"), fallback: false)
2π = 𝛼 + 𝛽. ✅
---
// Test string body.
#text("Text") \
#text(red, "Text") \
#text(font: "Ubuntu", blue, "Text") \
#text([Text], teal, font: "IBM Plex Serif") \
#text(forest, font: "New Computer Modern", [Text]) \
---
// Error: 11-16 unexpected argument
#set text(false)
---
// Error: 18-24 expected "normal", "italic", or "oblique"
#set text(style: "bold", weight: "thin")
---
// Error: 23-27 unexpected argument
#set text(size: 10pt, 12pt)
---
// Error: 11-31 unexpected argument: something
#set text(something: "invalid")
|
https://github.com/drupol/master-thesis | https://raw.githubusercontent.com/drupol/master-thesis/main/resources/typst/ch4-table-conclusion.typ | typst | Other | #set align(left)
#table(
columns: (1fr, 1fr),
stroke: none,
[#align(center)[Pros]],
table.vline(stroke: .5pt),
[#align(center)[Cons]],
table.hline(stroke: .5pt),
[
Facilitates collaboration and onboarding:
Reproducibility enables easier collaboration among researchers, developers,
as they can replicate and extend each other's work more efficiently.
],
[
Steep learning curve:
Implementing reproducibility practices may require learning new tools and
methodologies, which can be time-consuming and challenging.
],
table.hline(stroke: .5pt),
[
Transparency and trust:
By sharing the methods, data, and tools used in research and development,
other collaborators can verify and build upon the work, fostering a culture
of openness and collaboration.
],
[
Complexity:
The process of making software reproducible can be complex, especially if it
has not been setup from the beginning of the project.
],
table.hline(stroke: .5pt),
[
Improves software quality:
Reproducibility practices help in identifying and fixing bugs, improving the
software's overall quality and robustness.
],
[
Proliferation of package managers:
The existence of too many package managers that
are built without reproducibility in mind can add another layer of complexity when trying to build software reproducibly.
],
table.hline(stroke: .5pt),
[
Enhanced reliability and validity:
Reproducible results provide confidence that findings are accurate and not
due to random chance or specific initial conditions of a single experiment.
],
[
Factors limiting reproducibility:
Factors such as proprietary software, licensing issues, and evolving
hardware can pose challenges to achieving full reproducibility.
],
table.hline(stroke: .5pt),
[
Security and integrity:
Ensuring that software can be reliably rebuilt from its source helps in
detecting unauthorized changes, enhancing security, and maintaining the
integrity of the software supply chain.
],
[
Potential for misuse:
Over-reliance on automated reproducibility tools can lead to complacency,
where developers might not fully understand the underlying processes and
methodologies.
],
table.hline(stroke: .5pt),
[
Facilitates troubleshooting and debugging:
Reproducible experiments serve as a clear benchmark for comparison,
assisting teams in identifying discrepancies, tracing error origins, and
incrementally enhancing model performance.
],
[
Potential for stagnation:
Emphasis on reproducibility might slow down innovation as developers might
spend more time ensuring reproducibility rather than exploring new ideas and
methodologies.
]
)
|
https://github.com/polarkac/MTG-Stories | https://raw.githubusercontent.com/polarkac/MTG-Stories/master/stories/003%20-%20Gatecrash/012_The%20Hard%20Sell.typ | typst | #import "@local/mtgstory:0.2.0": conf
#show: doc => conf(
"The Hard Sell",
set_name: "Gatecrash",
story_date: datetime(day: 19, month: 03, year: 2013),
author: "<NAME>",
doc
)
Bartek heaved the last of the heavy wooden crates into the cart with a grunt. He leaned against the wall of the warehouse, breathing heavily, sweat running down his face. The sun was up, higher than he’d hoped, and it was already getting hot.
After catching his breath, he threw the heavy tarpaulin over the boxes and roped it in place.
Boss Zifka, also sweating despite having sat through the whole loadout, did his walkaround, inspecting Bartek’s work. As usual, he nodded his approval. Bartek had been loading for Zifka for a long time, and he knew what the merchant wanted. One of the things Zifka wanted was for Bartek to stay quiet about the occasional mismatch between the label on a crate and the weight and sound of its contents. Bartek was good at staying quiet. Zifka was good at paying him. They got along well.
#figure(image("012_The Hard Sell/02.jpg", width: 100%), caption: [], supplement: none, numbering: none)
After one last tug on the ropes, Zifka nodded again.
"Thank you for your help," he said, as he always did, shaking the young man’s hand. In his palm was the cold weight of a coin. Only the most zealous or inexperienced lawkeeper would go after the untaxed day labor that kept the market district running, but it never hurt to be discreet.
He glanced at the coin as he tucked it away. It was a banged-up one-zino piece, more than fair for a few hours of heavy lifting. That brought Bartek’s worldly wealth to six zinos—four in his coin purse plus one in each boot—along with eighty-some zibs and the clothes on his back. He started walking, a spring in his step. Funny how a heavy coin purse made you feel lighter.
Tin Street was brightly lit, awake with the sounds and smells of the market in what was now undeniably full day. Hawkers yelled about hats and potions and a dozen other things, the scents of fish and fruit and cheese mixed freely and strangely, and a Boros recruiter offered good coin to strong young men—"Just like this strapping fellow!" he said as Bartek passed by—who were willing to join the Wojeks. Bartek hurried on. He knew what happened to "strong young men" who stopped by those recruitment stands if they happened to have warrants outstanding. He wondered if that was all the recruitment stands were for.
#figure(image("012_The Hard Sell/04.jpg", width: 100%), caption: [], supplement: none, numbering: none)
"Jewelry!" cried one merchant, a gangly man with eyes like a weasel’s. "You there—tall fellow like you must have a lady friend to impress."
Bartek almost kept walking. But what was money if you couldn’t spend it? He sidled over, feigning disinterest, and surveyed the man’s wares. Most of this stuff was way out of his price range, but his eyes lingered on a thin metal ornament, cheaply made but elegantly shaped, suitable for hanging from a headband or necklace. He pointed at it.
"How much?" he asked.
The merchant looked him up and down with those weasely eyes. "She your girlfriend?"
Bartek shook his head.
"Who am I to stand in the way of young love?" said the man. He gave a theatric sigh. "One zino and it’s yours."
Bartek frowned. "I’ll give you eighty zibs," he said. "It’s pretty and all, but I still have to eat."
The man frowned right back. "I’m a romantic, friend, not a charity. Ninety zibs. That’s the best I can do."
"Eighty," said Bartek. "Please."
The merchant pursed his lips. "Fine," he said. "Eighty zibs, and you tell her you bought it from Imrich’s on Tin Street."
#figure(image("012_The Hard Sell/06.jpg", width: 100%), caption: [], supplement: none, numbering: none)
Bartek grinned. "Deal." He fished eighty zibs out of his coin purse and handed them over. #emph[Six zinos even] , he thought. He pocketed the little charm.
"Is that for your girlfriend?" piped a voice behind him.
He turned to see Nico, a thieving little rat of a boy who seemed to think they were friends. Bartek scowled and kept his hand on his coin purse.
"She’s not my girlfriend," he mumbled, and started walking. "Shouldn’t you be in jail or something?"
Nico kept pace with him, taking three steps for every two of Bartek’s. He actually should be in jail, for theft and vandalism, but that was true of a lot of Bartek’s friends.
"She’s pretty, though, huh?" said Nico.
"You wouldn’t know what to do with her," said Bartek.
It made him a little sick to talk about a friend like that, but he was speaking Nico’s language. #emph[Talk to a thug like a thug,] his mother told him once, #emph[and to a lady like a gentleman] .
Nico shrugged. "I bet she’d know what to do with me."
Bartek’s face went hot.
"Shut your mouth," he said. "Or I’ll shut it for you."
Nico scrambled ahead of him and got in his way. Bartek would have shouldered past, but something on the kid’s face made him stop. It looked strangely like genuine concern.
"You’re really sweet on her, aren’t you?" said Nico. "You’re in for a letdown here. She’s a shop girl, Bartek. It’s her job to flirt with you, to make you feel special. She’s just after your money."
Now Bartek did shove Nico out of his way.
"She knows I don’t have any money," he said, walking away.
"I bet she’d rather have your eighty zibs than your stupid jewelry," said Nico, but he didn’t follow.
After many curves and corners, ducking through alleys and strolling down thoroughfares, he found himself in an altogether more comfortable environment. People kept their eyes on the ground around here, and it had been ten minutes since he’d seen an arrester or a Wojek. Bane Alley. Home was at the far end, but he had a stop to make first.
The unassuming little stall was tucked off to the side, easy to miss if you didn’t know precisely where it was. Still, it was a welcoming little place, and it always had an interesting selection… but that wasn’t why Bartek stopped by every day.
Her name was Andra, and she was beautiful, well-spoken, and friendly. She seemed to cobble together a different outfit every day out of spare parts—but always somehow fashionable, and never overly modest.
#figure(image("012_The Hard Sell/08.jpg", width: 100%), caption: [], supplement: none, numbering: none)
As he walked up, she was talking easily with a woman in a cloak, showing off the binding of a particularly ornate old book. Without breaking her sales pitch, she met Bartek’s eyes over the woman’s shoulder and flashed him a smile like the noonday sun. He swallowed.
Eventually, the woman in the cloak made up her mind and forked over more money than Bartek made in a month for something she couldn’t eat, wear, or fight with. #emph[Six zinos even] , he thought again.
The woman in the cloak shuffled off, and Andra smiled at him.
"Bartek!" said Andra. "I was starting to get worried."
"Oh," he said. "Sorry."
She laughed at him.
"You don’t have to stop by every day, you know. You’re a busy guy. I’d understand."
"Of course I do," he said. He thumped his chest. "I’m your best customer."
"You’re consistent, anyway," she said.
It was an old joke. He stopped by nearly every day, but he hardly ever bought anything. He usually tried to stop by while she was still setting up, to make it less awkward when he didn’t buy anything. The simple truth was that she didn’t sell much that he could afford. Andra knew that, and didn’t seem to be in any hurry to chase him off.
"I’ve got something for you," he said.
"That’s funny," she said. "I was about to say the same thing. You first."
Carefully, he withdrew the little ornament and held it out. Andra smiled and took it from him, her fingers brushing against his. She held it up and examined it in the morning light.
"Cheap materials, but beautiful craftsmanship," she said. "Somebody loved this little piece of pewter."
"You like it?" he said.
"It’s beautiful," she said. "I don’t think I can give you much for it, though."
He flushed.
"It’s… I mean, I got it #emph[for] you," he stammered. "As a gift. At a place called Iprich’s or something, over on Tin Street. He wouldn’t sell it to me unless I promised to tell you where I got it."
"You bought this for me?" she asked.
"Yeah," he said. "I guess I did. It just… made me think of you."
"Common, but well put together?" she said, cocking an eyebrow.
He flushed again, and she laughed.
"Bartek, it’s beautiful," she said earnestly. "Thank you."
She brushed her hair aside, found an empty spot on her headband, and hooked the ornament to it.
"How does it look?" she asked.
"Beautiful," he said. "It fits right in."
#figure(image("012_The Hard Sell/10.jpg", width: 100%), caption: [], supplement: none, numbering: none)
She rolled her eyes at him. When he paid her compliments she liked to pretend he was joking, or exaggerating, or just trying to flatter her. Sometimes it upset him. This time he was in too good a mood.
"You said you had something for me?" he said.
"Oh," said Andra. "I do, but I’m afraid it’s not a gift."
"I wasn’t expecting one," he said.
She pulled a cloth-wrapped bundle out from under the counter.
"I’ve been saving this one for you," she said. "I know you’re strapped, but I picked this up cheap, and I wanted to give you a shot at it. It just… made me think of you."
She unwrapped the bundle and held out an exquisitely crafted dagger with a gently curved blade. The metal was dark, almost black, and finely polished. It was a gorgeous blade, and just the right size—small enough to wear openly without looking like a bravo, big enough to make people just a tiny bit nervous.
His heart sank. There was no way he could afford something like this.
"Five zinos," she said. "A special offer for my best customer."
"Are you serious?" he said. "It’s got to be worth twice that."
"Like I said, I got it cheap. And I really do think it would look good on you."
#emph[She just wants your money] , said Nico’s voice in his head. But she could probably get twelve zinos for it if she was patient. That was a lot of cash to give up just to fleece him personally.
That left one possibility: she really was making a deal for a friend. He swallowed. #emph[Six zinos even] .
"Try it on," she said, holding it out to him.
He took the blade and carefully tucked it in his belt. It felt good—heavy, but not too heavy. He practiced a draw. The metal was smooth, and the curve of the blade was gentle enough that it didn’t foul the draw. He put the dagger back in his belt.
"How does it look?" he asked.
"Dashing," she said. "Rugged. Little bit dangerous. It fits right in."
He rolled his eyes.
"That’s laying it on a bit thick, don’t you think?"
"Bartek, I’m serious," she said. "It looks really good on you."
He flushed again.
"Deal," he said. "Five zinos. I’ll be broke, but I’ll look good doing it."
He fished one zino out of his right boot and emptied the four in his coin purse onto the counter. #emph[One zino left] , he thought.
She swept the coins away in one smooth motion and smiled.
"Thank you," he said. "It might not be a gift, but you didn’t have to do that."
"Nope," she said. "I wanted to."
He grinned.
"I’d better get going," he said. "Lots of important swaggering to do."
"Oh yes," she said. "You’re a busy guy. I understand."
He flashed her one last smile and headed for home. And if there was a little swagger in his step, who could blame him?
It was early morning, dawn creeping down the alley as the sun cleared the surrounding buildings. Andra whistled as she set up shop, keeping an eye out for Bartek.
She had only just gotten things in order when she spotted his tall frame moving through the sparse morning crowd. He was on time today.
He had a big purple lump above one eye, and the finely crafted dagger was nowhere to be seen. It looked like he might hurry past, but she caught his eye and waved, and he walked over to the little stall.
"Bartek! What happened to you?" she asked. "Are you all right?"
"I’ll be fine," he said. He sounded tired as hell. "Couple of guys jumped me last night on my way to work. Bashed me in the head before I could get a look at them. Can’t say they got much for their trouble, but they took my new dagger."
#figure(image("012_The Hard Sell/12.jpg", width: 100%), caption: [], supplement: none, numbering: none)
"I’m so sorry, Bartek." She frowned. "Listen, I don’t usually do this, but if you want your five zinos back—"
He shook his head.
"It’s not your fault," he said. "It was mine to lose."
"I’m sorry," she said. He nodded wearily.
"I’ll be fine," he said. "You be careful who you buy from, okay? I think maybe that dagger might have been stolen, and these guys came to get it back. It could have been you they beat up."
"You’re sweet," she said. "I’ll be careful."
"I’m going to go sleep this off," he said. "Have a good day, okay?"
"You too," she said.
Andra watched him go. He was just a kid, and awfully nice for a former thug.
There weren’t really any customers yet, so she sat down behind the counter. She got out paper, ink, and pen and began a highly coded message to her superiors.
#emph[Item is now in possession of third party. Contact if more detail desired.]
She didn’t know whether the knife was a murder weapon, stolen goods, or whatever else, and she didn’t want to. All she knew was that the House Dimir wanted it sold to someone in particular, and they didn’t want any link between its new owners and her.
#emph[Courier survives but remains unaware of role in delivery.]
It was a favorite trick of hers: sell someone an illicit item, then arrange for it to be stolen by the real buyers. It broke the trail that led to her, and on top of that, she’d gotten paid twice for the same goods. Usually, the courier didn’t fare well in the bargain, but this time she’d asked the buyer to leave the kid alive. She’d been relieved to see Bartek’s face, even banged up as it was.
#emph[Profit from primary sale: 20 zinos. Profit from secondary sale: 5 zinos. Value of additional goods acquired during secondary transaction:]
She twirled the little headband ornament in her fingers and smiled.
#emph[negligible.]
She blew on the ink to dry it, folded the letter, and tucked it away.
He really was a sweet kid.
|
|
https://github.com/qo/term | https://raw.githubusercontent.com/qo/term/main/examples/file/file.typ | typst | #import "../../term.typ": term
#let ps1 = "$"
#let input = read("./in")
#let output = read("./out")
#let content = raw(ps1 + " " + input + output)
#figure(
term(
content: content
),
caption: "Listing files in a directory",
)
|
|
https://github.com/ecrax/packages | https://raw.githubusercontent.com/ecrax/packages/main/local/island/0.1.0/lib.typ | typst | #import "@preview/quick-maths:0.1.0": shorthands
// Workaround for the lack of an `std` scope.
#let std-bibliography = bibliography
#let contents = (depth: 1) => {
show outline.entry: it => {
v(-10pt, weak: true)
grid(
columns: (20pt, 1fr),
column-gutter: 10pt,
link(it.element.location())[#align(right)[*#it.page*]],
link(it.element.location())[#text(fill: black.lighten(33%))[#it.body]],
)
}
outline(depth: depth, title: none)
}
#let quote = (body) => {
align(center)[
#line(length: 80%, stroke: primary)
#text(style: "italic")[#body]
#line(length: 80%, stroke: primary)
]
}
#let br = linebreak(justify: true)
#let col(body, height: none) = {
let content = columns(2, gutter: 0.4in, body)
if height != none [
#box(height: height)[#content]
] else [
#content
]
}
#let blurb(body) = {
text(size: 13pt)[#body]
v(0.3in)
}
#let content-page = (lang: "de", subtext: none, depth: 1) => {
if lang == "de" {
heading(level: 1)[Inhaltsverzeichnis]
} else if lang == "en" {
heading(level: 1)[Table of Contents]
}
col[
#box(height: 80%)[
#align(horizon)[#contents(depth: depth)]
]
#colbreak()
#if subtext != none {
box(height: 100%)[
#align(bottom)[
#emph(subtext)
]
]
}
]
v(0.4in)
pagebreak()
}
#let island(
// The paper's language.
lang: "de",
// The paper's title.
title: "",
// The paper's subheading.
subheading: none,
// The primary color to use in the paper.
primary: rgb("#303154"),
// An array of authors. For each author you can specify a name,
// and a matriculation number.
authors: (),
// The semester the paper was written in.
semester: "WS2023/24",
// Whether to display the title page.
show-title-page: true,
// The image to display on the title page.
img: none,
// Whether to display the outline.
show-outline: true,
// The depth of the outline to display.
outline-depth: 1,
// The subtext to display below/next to the outline.
outline-subtext: none,
// The result of a call to the `bibliography` function or `none`.
bibliography: none,
// The paper's contents.
body,
) = {
show heading: h => {
set text(font: "Satoshi", fill: black, weight: 700)
set block(spacing: 1em)
h
}
show heading.where(level: 1): h => {
stack(
dir: ltr,
place(left, dx: -0.5in, rect(height: 13pt, width: 0.4in, fill: primary)),
text(size: 18pt, h),
)
v(0.4in)
}
show par: set block(spacing: 1.4em)
show cite: set text(fill: primary)
show link: set text(fill: primary)
show figure: set text(size: 9pt)
show: shorthands.with(
($+-$, $plus.minus$),
($|-$, math.tack),
($=>$, math.arrow.r.double),
($<==>$, math.arrow.l.r.double),
)
set document(title: title, author: authors.map(a => a.name))
set text(font: "Erode", fill: black.lighten(33%), lang: lang)
set par(justify: true)
if not img == none {
place(
horizon,
dx: -0.5in,
dy: -1.1in,
image(img, height: 89%, width: 100% + 2.4in),
)
}
let footer = () => {
locate(loc => {
if loc.page() == 1 and show-title-page { return }
let elems = query(selector(heading.where(level: 1)).before(loc), loc)
let section = if elems == () {} else { elems.last().body }
grid(columns: (1fr, 20pt, 1fr), align(left)[
#text(size: 10pt, fill: black.lighten(70%))[#title]
], align(center)[
*#counter(page).display()*
], pad(left: 15%, align(right)[
#text(size: 10pt, fill: black.lighten(70%))[#section]
]))
})
}
if show-title-page {
align(bottom)[
#text(font: "Satoshi", 1.1em, semester)
\-
#text(
font: "Satoshi",
1.1em,
datetime.today().display("[month repr:long] [day], [year]"),
)
#v(1.2em, weak: true)
#text(font: "Satoshi", weight: 700, title, size: 24pt)
#if subheading != none {
v(-0.9em)
text(font: "Satoshi", size: 16pt, subheading)
}
// Author information.
#pad(
// top: 0.7em,
right: 20%,
grid(
columns: (1fr,) * calc.min(3, authors.len()),
gutter: 1em,
..authors.map(author => align(start)[#text(font: "Satoshi", [
*#author.name* \
#author.matnr
])
]),
),
)
#v(-8mm)
]
pagebreak()
}
set page(
margin: (bottom: 1in, rest: 0.5in),
footer-descent: 0.5in,
footer: footer(),
header-ascent: -0.18in,
header: if not show-title-page {
locate(
loc => if [#loc.page()] == [1] {
v(10cm)
grid(
columns: (1fr, 3fr, 1fr),
align(left, none),
align(center, none),
align(right, authors.map(author => align(start)[#text(font: "Satoshi", [
*#author.name* -
#author.affiliation
])
]).join(", ")),
)
},
)
} else {
none
},
)
if show-outline {
content-page(lang: lang, subtext: outline-subtext, depth: outline-depth)
}
// Display the paper's contents.
body
// Display bibliography.
if bibliography != none {
show std-bibliography: set text(11pt)
set std-bibliography(title: none, style: "ieee")
pagebreak()
if lang == "de" {
heading(level: 1)[Literaturverzeichnis]
} else if lang == "en" {
heading(level: 1)[References]
}
col[
#par(justify: false, leading: 0.5em)[
#bibliography
]
]
}
} |
|
https://github.com/HarryLuoo/sp24 | https://raw.githubusercontent.com/HarryLuoo/sp24/main/Physics311/reviewNotes/apnd.typ | typst | #set math.equation(numbering:"1")
//useful equations and notes
= Appendix
+ Taylor expansion:
$
lr(f(x)|)_0 approx f(a) + f'(a)(x-a) + f''(a)(x-a)^2/2
$
+ small angle approximation:
$
sin(theta) approx theta quad
cos(theta) approx 1-theta^2/2
$
|
|
https://github.com/Qi-Zhan/abstract_algebra | https://raw.githubusercontent.com/Qi-Zhan/abstract_algebra/main/main.typ | typst | #import "theorems.typ": *
#import "@preview/commute:0.2.0": node, arr, commutative-diagram
#show: thm-rules.with(qed-symbol: $square$)
#import "template.typ": *
#show: template.with(
title: [抽象代数笔记],
authors: (
(
name: "詹奇",
),
),
lof: false,
lot: false,
lol: false,
bibliography_file: none,
paper_size: "a4",
cols: 1,
code_font: "Cascadia Mono",
accent: "#DC143C",
)
#show link: underline
#let theorem = thm-plain(
"定理",
outset: 1em,
padding: (y: 0.6em),
fill: rgb("#eeffee"),
)
#let corollary = thm-plain("推论", base: "Theorem")
#let definition = thm-def("定义", outset: 1em, padding: (y: 0.6em), fill: rgb("#eeeeff"))
#let remark = thm-rem("注记")
#let proof = thm-proof("证明")
#let example = thm-plain("例子")
#let lemma = thm-plain("引理")
#set text(
font: "Songti SC",
)
本文是刘思齐老师的#link("https://space.bilibili.com/85657899/channel/collectiondetail?sid=3808884")[抽象代数课程]笔记。
= 域与线性空间
== 定义与例子
#definition("域")[
一个域系指以下资料:
1. 集合 $F$, 有 $1_F, 0_F in F$ 满足 $1_F != 0_F$, 有时简写为 $1, 0$.
2. $F$ 上的加法记为 $+$, 满足加法结合律, 加法交换律, 有加法单位元 $0$ 与加法逆元 $-a$. (这保障了加法逆元是唯一的).
3. $F$ 上的乘法记为 $*$, 满足乘法结合律, 乘法交换律, 有乘法单位元 $1$, 对于非零元 $a$, 有乘法逆元 $a^(-1)$. (这保障了乘法逆元是唯一的).
4. 乘法对加法的分配律成立.
]
#remark[
我们记 $F^*$ 为 $F$ 中所有非零元素的集合.
]
为了说明为什么我们要求 $0_F != 1_F$, 有以下引理:
#lemma[
1. $0_F dot 0_F = 0_F$.
2. $forall x in F, x dot 0_F = 0_F$
]
#proof[
1. $0_F = 0_F + 0_F = 0_F dot 0_F + 0_F dot 0_F$, 两边减去 $0_F dot 0_F$ 即得.
2. $x dot 0_F = x dot (0_F + 0_F) = x dot 0_F + x dot 0_F$, 两边减去 $x dot 0_F$ 即得.
]
由此可见, 若 $0_F = 1_F$, 那么 $F$ 中所有元素满足 $x = x dot 1_F = x dot 0_F = 0_f$, 这显然不是我们所期望的.
同理, 若对于域 $F$ 上的 $0_F$ 有逆元, 那么我们有 $0_F = a dot 0_F = 1_F$, 又推出了域中所有元素都是 $0_F$.
#example("域")[
1. 有理数域 $QQ$, 实数域 $RR$, 复数域 $CC$, 对于我们熟知的加法和乘法运算构成域.
2. $F = QQ(sqrt(2)) = { x + sqrt(2) y | x, y in QQ}$.
3. $F = QQ(root(3, 2)) = {x + root(3, 2) y | x, y in QQ}$
4. $F = QQ(sqrt(2), sqrt(3)) = {x_1 + x_2 sqrt(2) + x_3 sqrt(3) + x_4 sqrt(4) | x_i in QQ}$.
5. 任取素数 $p$, $F = ZZ_p = {0, 1, 2, ..., p-1}$, 其中加法和乘法都是模 $p$ 的. 其中乘法逆的存在是不显然的. 对于 $F$ 中任意一个非零元 $k$, 有, 我们考虑映射 $T: F_P^* -> F_P^*: y |-> k y $, 易证 $T$ 是双射, 从而存在逆元 $m$ 使得 $k m = 1$.
6. 设 $F$ 是一个域, 则 $F(x) = { P(x) / Q(x) | P(x), Q(x) in F[x], Q(x) != 0 }$ 同样构成域.
7. $k = CC(x, sqrt(x^3 + 2))$, 可以视作 $CC(x)(y)$ 其中 $y^2 = x^3 + 2$, 则 $k = {R_1(x) + R_x(y) | R_1, R_2 in CC(x)}$.
]
#definition("线性空间")[
设 $F$ 是一个域, $V$ 是一个集合, 若 $V$ 上定义了加法运算 $+: V times V -> V$, 以及数乘运算 $*: F times V -> V$, 满足以下条件:
1. 对于任意 $u, v, w in V$, 有 $u + (v + w) = (u + v) + w$.
2. 对于任意 $v in V$, 有 $v + 0 = v$.
3. 对于任意 $v in V$, 存在 $w in V$, 使得 $v + w = 0$.
4. 对于任意 $v in V$, 有 $1 v = v$.
5. 对于任意 $a, b in F, v in V$, 有 $a(b v) = (a b)v$.
6. 对于任意 $a in F, u, v in V$, 有 $a(u + v) = a u + a v$.
7. 对于任意 $a, b in F, v in V$, 有 $(a + b)v = a v + b v$.
]
线性空间的观点对于研究域的结构有很大的帮助, 例如我们可以将 $QQ(sqrt(2))$ 视作 $QQ$ 上的二维线性空间. $RR$ 可以视作 $QQ$ 上的无穷维线性空间.
#example[
$FF_4 = FF_2(alpha) = {x + alpha y | x, y in FF_2}$. 其中的问题是我们该取什么样的 $alpha$. 考虑 $FF_2[x]$ 上的所有二次多项式 $f(x) = x^2 + p x + q$, 及 $x^2, x^2 + x, x^2 + 1, x^2 + x + 1$. 其中前三个都是可约的, 所以我们取 $alpha$ 满足 $alpha^2 + alpha + 1 = 0$.
]
== 域的同态
我们先从线性空间上的同态(线性映射)开始.
#definition("线性映射")[
设 $V_1, V_2$ 是域 $F$ 的线性空间, 若映射 $f: V_1 -> V_2$ 满足:
1. 对于任意 $u, v in V_1$, 有 $f(u + v) = f(u) + f(v)$.
2. 对于任意 $a in F, v in V_1$, 有 $f(a v) = a f(v)$.
那么我们称 $f$ 是一个线性空间的同态, 即线性映射.
]
类似地, 我们可以定义域的同态.
#definition("域的同态")[
设 $F_1, F_2$ 是域, 若映射 $f: F_1 -> F_2$ 满足:
1. $f(0_F_1) = 0_F_2, f(1_F_1) = 1_F_2$.
2. 对于任意 $a, b in F_1$, 有 $f(a + b) = f(a) + f(b)$.
3. 对于任意 $a, b in F_1$, 有 $f(a b) = f(a) f(b)$.
那么我们称 $f$ 是域的同态.
]
不同于群和环的同态, 事实上域的同态是一个"没什么用"的概念, 有下面的定理:
#theorem[
设 $F_1, F_2$ 是域, $f: F_1 -> F_2$ 是域的同态, 则 $f$ 是单射.
]
#proof[
设 $a, b in F_1$ 满足 $f(a) = f(b)$. 设 $x = b - a$. 若 $x != 0$, 那么存在 $y in F_1$, 使得 $x y = 1$. 那么有 $0 dot f(y) = (f(b) - f(a)) dot f(y) = f(1) = 1$, 矛盾. 所以 $x = 0$, 即 $a = b$.
]
这也就说明若存在一个 $phi: F_1 -> F_2$, 那么我们视 $F_1$ 为 $F_2$ 的子域, 所以在研究域的时候, 我们不关心域的同态, 而更关心子域和域扩张的概念.
#definition("子域与扩域")[
设 $F$ 是域, 若 $E$ 是 $F$ 的子集, 且 $E$ 也构成域, 那么我们称 $E$ 是 $F$ 的子域, 同时称 $F$ 是 $E$ 的扩域, 记为 $F "/" E$.
]
#definition("域的同构")[
设 $F_1, F_2$ 是域, 若存在双射 $phi: F_1 -> F_2$, 且满足域的同态, 那么我们称 $F_1$ 与 $F_2$ 是同构的. 若 $F_1 = F_2$, 我们称 $phi$ 是域 $F_1$ 的自同构. 我们称在自同构下不变的元素为域 $F_1$ 的不动域.
]
#example[
1. $RR "/" QQ, CC "/" RR, QQ(sqrt(2)) "/" QQ, FF_4 "/" FF_2$.
2. $f: CC -> CC, x + i y |-> x - i y$ 是域 $CC$ 的自同构, 其中不动域是实数域 $RR$.
3. $QQ(sqrt(2))$ 与 $QQ(sqrt(3))$ 不存在同态.
]
事实上, $QQ, FF_p$ 是某种程度上的"最小"域, 我们有以下定理:
#theorem[ $QQ, FF_p$ 没有真子域. ]
#theorem[
若 $F$ 是 $E$ 的扩域, 则 $F$ 是 $E$ 上的线性空间, 我们记 $[F: E]= dim_E F$, 称为 $F "/" E$ 的次数. 若 $[F: E] < oo$, 则称 $F "/" E$ 为有限扩张.
]
== 域的特征
#definition("域的特征")[
设 $F$ 是域, 若存在最小的正整数 $n$, 使得 $n 1_F = 0_F$, 那么我们称 $n$ 为域 $F$ 的特征, 记为 $"char"(F) = n$. 若不存在这样的 $n$, 我们称 $F$ 的特征为 $0$.
]
容易看出如果域的特征是正的, 那么它一定是素数. 若 $"char"(F) = 0$, 那么 $QQ$ 是 $F$ 的子域; 若 $"char"(F) = p$, 那么 $FF_p$ 是 $F$ 的子域.
(注意这里的子域可以看作是存在一个域同态而不是严格的包含). 这就是说明了每个域都是 $QQ$ 或 $FF_p$ 的扩域.
在正特征的域上有一个有趣的运算. 若 $"char"F = p > 0$, 我们考虑 $(x+y)^p $, 由二项式定理, 我们有:
$(x+y)^p = x^p + y^p + C_p^1 x^(p-1) y + ... + C_p^(p-1) x y^(p-1) + y^p = x^p + y^p$.
我们记 $sigma: F->F$ 满足 $x|-> x^p$, 由上面的性质容易发现 $sigma$ 是一个域同构, 我们称 $sigma$ 为域 $F$ 的 Frobenius 自同构.
== 域的扩张
#definition[
设 $E "/" F$ 是一个域扩张, 对于 $E$ 中的子集 $S$, 有 $F(S)$ 为 $E$ 中包含 $F union S$ 的最小子域, 称为 $F$ 在 $S$ 上生成的域. 若 $S$ 是有限的且 $F(S) = E$, 我们称 $E$ 是由 $F$ 上的有限生成扩张. 若对 $E$ 的任意有限子集, $F(S) != E$, 则称 $E$ 为无限生成的.
]
#example[
1. $QQ(sqrt(2))$ 是 $QQ$ 上的有限生成扩张, 也是有限扩张.
2. $RR(x)$ 有理函数域是 $RR$ 上的有限生成扩张, 但不是有限扩张.
3. $F = QQ$, $E = QQ(2^(1/2^k)), k=1,2,...$. 我们考虑逐步添加元素. $E_1 = QQ(2^(1/2)), E_2 = E_1(2^(1/2^2)) = QQ(2^(1/2^k))$, 容易得到 $E_k = QQ(2^(1/2^k))$. $F = E_0 subset.eq E_1 subset.eq ..., E = union.big_(k=1)^oo E_k$.
]
我们研究的域扩张要解决的问题: 一个*尽可能简单*的域扩张是什么样的?
#theorem[
有限扩张一定是有限生成扩张, 反之不然.
]
#proof[
若 $[E:F] = n$, 可推得 $E = "Span"_F(e_1, ..., e_n)$, $E = F(e_1, ..., e_n)$.
]
#definition("代数扩张与超越扩张")[
设扩域 $E"/"F$, 若 $u in E$ 存在 $f(u) = 0, f != 0, f in F[x]$, 则称 $u$ 为 $F$ 上的代数元. 若 $E/F$ 中的每个元素都是代数元, 则称 $E"/"F$ 为代数扩张. 若存在 $u in E$ 使得 $u$ 不是任何 $f in F[x]$ 的根, 则称 $u$ 为超越元, $E"/"F$ 为超越扩张.
]
#example[
1. $QQ(sqrt(2))$ 为代数扩张.
2. $QQ(x), QQ(pi)$ 为超越扩张.
]
现在我们有了三个“不太大”的扩张, 有限扩张, 有限生成扩张和代数扩张, 我们的目标是理解这三个概念之间的关系, 从而理解域上较小的扩张是什么样的.
我们先证明一些有关代数数的性质.
#lemma[
设 $E "/" F$, $alpha, beta$ 是 $F$ 上的代数元, 则 $alpha + beta$ 和 $alpha beta$ 也是代数元.
]
这一引理有不同的证法. 一种证法基于对称多项式的理论直接构造出对应的多项式, 我们这里给出另一种证法.
#proof[
设 $f(alpha) = 0, f in F[x], g(beta) = 0, g in F[x], deg f = n, deg g = m$. 定义 $h(y) = R_(x)(f(x), g(y-x)) in F[y]$. 其中 $R_x(A[x], B[x])$ 为多项式 $A, B$ 关于变量 $x$ 的结式. 我们断言 $h(alpha + beta) = 0$, 这是因为 $f(x)$ 与 $g(alpha + beta -x)$ 有公共根 $x = alpha$. 对于 $alpha beta $ 同理.
]
现在我们来看具体的关系.
#theorem[
有限扩张一定是代数扩张, 反之不然.
]
#proof[
设 $[E "/" F] = n$ 是有限扩张, 对于任意 $u in E$, 我们要找 $f in F[x]$ 使得 $f(u) = 0$. 考虑 $1, u, u^2, ... in E$. 由 $dim_F (E) = n$, 所以 $1, u, u^2, ..., u^n$ $F-$线性相关, 所以存在 $b_0, ..., b_n in F$ 不全为0, 使得 $b_0 + b_1 u + ... + b_n u^n = 0$, 故 $u$ 是代数元.
反例: $F = QQ$, $E = QQ(2^(1/2^k)), k=1,2,...$ 是代数扩张, 但不是有限生成扩张, 更不是有限扩张.
]
由上文的例子我们知道代数扩张不能推出有限生成扩张, 有限生成扩张也不能推出代数扩张.
看起来代数扩张和有限生成扩张都是不太好的扩张, 但下面的定理告诉我们, 有限生成扩张和代数扩张的交集是一个很好的扩张.
#theorem[
有限生成的代数扩张是有限扩张. 具体来说, 对于域扩张 $E "/" F$, 以下两个事实等价:
1. $E "/" F$ 是有限扩张.
2. $E = F(u_1, ..., u_n)$, 其中 $u_1, ..., u_n$ 是 $F$ 上的代数元. 此时 $E "/" F$ 是代数扩张.
]
1. (1) => (2). 设 $[E: F] = n$, $u_1, ... u_n$ 是 $E "/" F$ 的基, 则 $E = F(u_1, ..., u_n)$. 因为 $E "/" F$ 是代数扩张, 所以 $u_1, ..., u_n$ 是代数元.
2. (2) => (1). 为了证明这一点, 我们需要一些定义和引理.
#definition("中间域")[
设 $E "/" F$, 则域 $K$ 是 $E$ 和 $F$ 的中间域, 若 $F subset.eq K subset.eq E$.
]
#example[
下图即为中间域的一个例子.
#align(center)[
#commutative-diagram(
node((0, 1), $QQ(sqrt(3))$),
node((1, 0), $QQ$),
node((-1, 0), $QQ(sqrt(2), sqrt(3))$),
node((0, -1), $QQ(sqrt(2))$),
arr((0,1), (-1, 0), ""),
arr((0,-1), (-1, 0), ""),
arr((1, 0), (0, 1), ""),
arr((1,0), (0, -1), "")
)]]
#lemma("维数公式")[
设 $E "/" F$ 是有限扩张, $K$ 是一个中间域, 则 $[E:F] = [E:K][K:F]$.
]
#proof[
有限维线性空间的线性子空间自然也是有限的.
设 $u_1, ..., u_n$ 是 $K "/" F$ 的基, $v_1, .., v_m$ 是 $E "/" K$ 的基, 下面构造 $E "/" F$ 的基.
对于 $beta in E$, 存在 $alpha_1, ..., alpha_m in K$ 使得 $beta = alpha_1v_1+...+ alpha_m v_m$, 对于每个 $alpha_i$ 存在 $a_(i 1), ..., a_(i n) in F$, 使得 $alpha_1 = a_(i i) u_1 +...+ a_(i n) u_n$, 整理可得 $beta = Sigma_(i=1)^m Sigma_(j=1)^n a_(i j) u_j v_i$. 所以 $dim_F E <= n dot m$.
下证 $u_j v_i$ 线性无关. 设 $Sigma_(i,j) c_(i j) u_j v_i = 0$, 推得 $Sigma_i (Sigma_j c_(i j) u_j)v_i = 0$. 由 $v_1, ..., v_m$ 线性无关, 所以 $Sigma c_(i j) u_j = 0$, 由 $u_1, ..., u_n$ 线性无关, 得 $c_(i j) = 0$.
]
#lemma[
单代数扩张是有限扩张.
]
#proof[
设 $E = F(u)$, $u$ 是 $F$ 上的代数元, 我们要证明 $[E:F] < oo$. 设 $f in F(x), f != 0$ 使得 $f(u) = 0$, 并且 $f$ 是满足该条件的次数最小的首一多项式. 设 $deg f = n$, 则 $E = f(u) = "Span"_F (1, u, ..., u^(n-1))$, 由此 $dim_F E = n$, 是有限的.
]
回到我们想要证明的结论, 我们同样可以逐个添加元素. $F subset.eq F(u_1) subset.eq F(u_1, u_2) subset.eq ... subset.eq F(u_1, ..., u_n)$. 每次的扩张都是单代数扩张, 也就是有限扩张, 维数就是有限的. 而由维数公式我们知道最终的维数也就是 $[F(u_1, u_2): F(u_1)] dot [F(u_1): F] dot ...$.
至此, 我们证明了有限生成的代数扩张一定是有限扩张. $square$
#theorem[
若 $F subset.eq K subset.eq E$, 其中 $K "/" F$ 代数, $E "/" K$ 代数, 那么 $E "/" K$ 代数.
]
#proof[
设 $alpha in E$, 存在 $f in K[x], f != 0$, $f(alpha) = 0$. 设 $f(x) = x^n + a_1 x^(n-1) + ... + a^n, a_i in K$. 设 $K' = F(a_1, ..., a^n)$, 注意到 $a_1, ..., a_n$ 在 $F$ 上代数, 则 $K' "/" F$ 是有限扩张. 再注意到 $K'(alpha) "/" K'$ 是一个单扩张, 所以 $K'(alpha) "/" K'$ 是有限扩张, 可得 $[K'(alpha): F] = [K'(alpha)] [K':F] = oo$, 也是有限扩张. 因为 $F subset.eq K'$, 所以 $F(alpha) subset.eq K'(alpha)$ 也是有限扩张.
所以 $F(alpha)$ 是代数扩张, $alpha$ 是代数元.
]
== 代数闭包
上一节我们考虑的是小的扩张长什么样, 这一节我们讨论大的扩张, 尤其是大的代数扩张.
#definition("代数闭包")[
设 $F$ 是域, 若 $E "/" F$ 是代数扩张, $K = {alpha in E | alpha "在" E "代数"}$, 显然 $K$ 是中间域, 我们称 $K$ 是 $F$ 在 $E$ 中的代数闭包.
若 $K$ 没有真代数扩张, 我们称 $K$ 是代数闭域.
若 $K "/" F$ 是代数扩张且 $K$ 是代数闭域, 我们称 $K$ 是 $F$ 的一个(绝对)代数闭包.
]
例如 $CC$ 就是代数闭的.
#theorem[
$QQ$ 在 $CC$ 中的相对代数闭包就是 $QQ$ 的一个绝对代数闭包.
]
#proof[
我们证明一个更一般的版本: $E$ 是代数闭的, $F$ 是 $E$ 的子域, $K$ 是 $F$ 在 $E$ 中的代数闭包, 则 $K$ 是 $F$ 的绝对代数闭包.
只需证明 $K$ 是代数闭的. 假设 $K'$ 是 $K$ 的一个代数扩张, $alpha in K'$, 则由 $alpha$ 的极小多项式 $f(x) in K[x]$, 因为 $K subset.eq E$, 所以 $f(x) in E[x]$, 所以 $f(x) = (x-alpha_1) ... (x-alpha_n) in K[x], a_i in E$. 另一方面 $alpha_i$ 是 $K$ 上的代数元, 因为 $K$ 是相对代数闭包, 所以 $a_i in K$, 所以 $f(x) = x - alpha$. 最终我们得到 $K' = K$.
]
== Galois 群初探
一个自然的问题是我们还没有定义抽象的群, 那么该如何讨论 Galois 群. 事实上在 Galois 研究时他并没有采用抽象的群概念, 而是考虑一种特殊的群, 即*置换*群.
#definition("对称群")[
设集合 $X$, $S(X) = {sigma: X -> X | sigma "是双射"}$, 我们可以定义映射的复合和逆运算, 也有单位映射 $e$. 事实上它满足如下性质:
1. $(sigma tau) mu = sigma (tau mu)$.
2. $sigma e = e sigma = sigma$.
3. $sigma sigma^(-1) = sigma^(-1) sigma = e$.
我们称 $(S, e)$ 是 $X$ 上的对称群.
]
#remark[
事实上上述的性质其实就是抽象群的定义.
]
我们一般不需要研究整个置换, 而是研究一部分的封闭子集, 也就引出了置换群的概念.
#definition("置换群")[
若 $G subset.eq S$ 满足于任意 $sigma, tau in G$, 有 $sigma tau in G$, $sigma^(-1) in G$, 则称 $G$ 是 $X$ 上的置换群.
]
更进一步的, 我们可以定义域 $E$ 上的自同构群, 记为 $"Aut"(E) = {sigma in S(E) | sigma(0) = 0, sigma(1) = 1, sigma(alpha + beta) = sigma(alpha) + sigma(beta), sigma(alpha beta) = sigma(alpha) sigma(beta), ...}$.
#definition("Galois 群")[
设 $E "/" F$ 是域扩张, 我们定义 $"Gal"(E "/" F) = {sigma in "Aut"(E) | sigma|_F = id_F}$, 称为 $E "/" F$ 的 Galois 群.
]
#theorem[
若 $E "/" F$ 是有限扩张, 则 $"Gal"(E "/" F)$ 是有限群.
]
#proof[
设 $E = "Span"_F(u_1,...,u_n)$, 其中 $u_n$ 在 $F$ 上代数. 对于 $u_1$, 有极小多项式 $f_1 in F[x]$, 满足 $f_1(u_1) = mu_1^n + a_1 u_1^(n-1) + ... + a_n = 0, a_i in F$.
设 $sigma in "Aut"(E), sigma|_F = id_F$, 考虑 $sigma$ 作用 $f_1$. $sigma(f_1(u_1)) = sigma(0) = 0 = sigma(u_1^n + ... + a_n) = f_1(sigma(mu_1))$.
这就说明了对于 $X_1 = {sigma in E | f_1(alpha) = 0}$, $sigma|x_1$ 是 $X_1$ 的一个置换. 同样的对于任意 $u_1$ 取 $f_i$, 定义 $X = union.big_(i=1)^n X_i$, $sigma$ 是 $X$ 上的一个置换. 由于 $X$ 是有限集, 所以 $sigma$ 是有限的.
]
#definition("不动域")[
设 $E$ 是一个域, 且 $G <= "Aut"(E)$, 定义 $"Inv"(G) = {alpha in E | sigma(alpha) = alpha, sigma in G}$, 称为 $G$ 的不动域.
]
#theorem("Artin 引理")[
设 $E$ 是域, $G <= "Aut"(E)$, 则 $"Inv"(G)$ 是 $E$ 的子域, 且 $[E:F] <= |G|$, 于是 $E "/" F$ 是有限扩张.
]
#proof[
设 $G = {eta_1 = e, ..., eta_n}, |G| = n$. 下证对于 $m > n$, $E$ 中的任意 $u_1, ..., u_m$ 是线性相关的. 考虑 $eta_j (x_1mu_1 + ... + x_mu_m) = x_1 eta_j(mu_1) + ... + x_m eta_j(mu_m) = 0$, 一定有非零解, 所以存在 $(x_1, ..., x_m) in E^m$. 下证 $x_j in F$.
我们从这些解挑一个含0元素最多的解, 记为 $x = x_1, ..., x_m$, 不妨假设 $x_1 != 0, x_1 = 1$, 下证 $x_2, ..., x_m in F$. 假设 $x_2 in.not F$, 则存在 $eta in G$ 使得 $eta(x_2) != x_2$, 考虑 $eta(x) = (1, eta(x_2), ..., eta(x_m))$, 显然 $eta(x)$ 仍是方程的解, 且 $eta(x)$ 0 的个数和 $x$ 中个数一样多.
考虑 $eta(x) - x$ 仍然是方程组的解, 但包含更多的0, 另一方面 $eta(x_2) - x_2 !=0 $, 矛盾!
]
#remark[
事实上我们可以证明 $[E: F] = |G|$, 但这需要一些额外的知识.
]
有了这两个方向的引理, 我们可以考虑它们的复合, 就有了下面两个问题:
Q1. $E "/" F$ 是有限扩张, $G = "Gal"(E "/" F)$ 是有限群, 我们可以定义 $F' = "Inv"(G)$ 由定义可知 $F subset.eq F'$. 问题是 $F'$ 与 $F$ 能否相等?
Q2. 有 $E$ 域, $G <= "Aut"(E)$, 我们有 $F = "Inv"(G)$, 其中 $E "/" F$ 是有限扩张, 于是 $G' = "Gal"(E "/" F)$ 是有限群, 由定义可知 $G subset.eq G'$. 问题是 $G$ 与 $G'$ 能否相等?
对于 Q2, 我们的结论是肯定的, 这也被称为 Artin 定理.
而对于 Q1, 则不能保证, Galois 理论研究的就是在什么样的有限扩张 $E "/" F$ 可以使得 $"Inv"("Gal"(E "/" F)) = F$.
#example[
1. $E = QQ(sqrt(2)), F = QQ$, 易知 $"Gal"(E "/" F) = { id }$, 所以 $F' = E != F$. 我们考虑 $alpha = root(3, 2)$, 极小多项式 $f(x) = x^3 - 2 = (x-alpha)(x^2 + alpha x + alpha^2)$. 可以看到另外两个复数根都不在 $E$ 中, 方程的其他根没有 $E$ 中.
2. $F = FF_2(T), E = F(sqrt(T)), sqrt(T) = s$, $E$ 可以写成 $"Span"_T (1,s)$, 考虑 $sigma: E -> E$ 是保 $F$ 的一个自同构, $sigma(1) = 1, sigma(s) = u$. 因为 $s^2 = T$, 所以 $sigma(s)^2 = sigma(T) = T$, 即 $u^2 = T$. 考虑 $u = a + b s, a, b in F$, $u^2 = a^2 + b^2 T = T$, 得到 $a^2 = T(1+b^2) = T(1+b)^2$. 考虑两边的次数, 只能有 $a = 0, b = 1$, 所以 $u = s$, 即 $sigma (s) =s$, 所以 $F' = E$.
]
为了避免这两种坏情况, 我们后面要引入分裂域, 正规扩张等概念.
对于这些问题的深入探讨, 要留到最后一部分, 等我们讨论完环论和群论的基础知识.
= 环与模
== 定义与例子
#definition("环")[
设 $R$ 是一个集合, 定义了加法运算 $+: R times R -> R$, 以及乘法运算 $*: R times R -> R$, 满足以下条件:
1. 对于任意 $a, b, c in R$, 有 $a + (b + c) = (a + b) + c$.
2. 对于任意 $a, b in R$, 有 $a + b = b + a$.
3. 存在 $0 in R$, 使得对于任意 $a in R$, 有 $a + 0 = a$.
4. 对于任意 $a in R$, 存在 $-a in R$, 使得 $a + (-a) = 0$.
5. 对于任意 $a, b, c in R$, 有 $a(b c) = (a b) c$.
6. 对于任意 $a, b, c in R$, 有 $a(b + c) = a b + a c$.
7. 对于任意 $a, b, c in R$, 有 $(a + b) c = a c + b c$.
我们称 $(R, +, dot)$ 构成一个环.
若存在 $1_R in R$ 满足 $a 1_R = 1_R a = a$, 称 $1_R$ 为单位元, 这样的环称为幺环.
若 $a b = b a$, 我们称 $R$ 是交换环.
]
#example("环")[
1. $ZZ, ZZ_m = {0, 1, dots, m -1}$.
2. $QQ, RR, CC$ 等所有的域都是环.
3. 多项式环.
4. 有线性空间 $V$, 则 $"End"(V)$ 是一个环.
5. 考虑 $R = m ZZ, m in NN, m >= 2$. $R$ 没有单位元.
6. $ZZ[i]$ 为 Gauss 整数环. $ZZ[eta_m], eta_m = e^(2pi i / n)$.
7. 设集合 $X$, 环 $R$, $R^X = {f: X -> R}$, 定义 $f + g = x |-> f(x) + g(x)$, $f g = x |-> f(x) g(x)$, 则 $R^X$ 是一个环.
8. 假设 $G$ 是有限群, $F$ 是群, 我们定义 $R = "Span"_F(G)$, 不难按定义写出 $R$ 的加法和乘法, 叫做 $G$ 的群代数, 这是群表示论的基础.
9. $HH = "Span"_RR (1, i, j, k)$,其中 $1, i, j , k$ 是四元数, 定义 $i^2 = j^2 = k^2 = -1, i j = k, j k = i, k i = j, j i = -k, k j = -i, i k = -j$, 这是一个含有单位, 非交换, 非零元可逆的环. 容易看出 $(a + b i + c j + d k)(a - b i - c j - d k ) = a^2 + b^2 + c^2 + d^2 > 0$.
]
#definition("模")[
设 $R$ 是一个环, $M$ 是一个集合, 定义了加法运算 $+: M times M -> M$, 以及乘法运算 $*: R times M -> M$, 满足以下条件:
1. 对于任意 $a, b, c in M$, 有 $a + (b + c) = (a + b) + c$.
2. 对于任意 $a, b in M$, 有 $a + b = b + a$.
3. 存在 $0 in M$, 使得对于任意 $a in M$, 有 $a + 0 = a$.
4. 对于任意 $a in M$, 存在 $-a in M$, 使得 $a + (-a) = 0$.
5. 对于任意 $a, b in R$, $x in M$, 有 $a(x + y) = a x + a y$.
6. 对于任意 $a, b in R$, $x in M$, 有 $(a + b) x = a x + b x$.
7. 对于任意 $a, b in R$, $x in M$, 有 $(a b) x = a (b x)$.
8. 对于任意 $x in M$, 有 $1 x = x$.
我们称 $(M, +, dot)$ 构成一个 左$R$-模. 同理可以定义右$R$-模.
]
#example("模")[
1. 域上的线性空间是模.
2. $ZZ_m, ZZ times ZZ_m -> ZZ_m$, 定义 $(a, overline(x)) |-> overline(a dot x)$. 更进一步的, 如果 $G$ 是交换群, 可以定义 $ZZ times G -> G$, 其中 $(a, g) |-> g^a$, 我们称为 $ZZ-j$ 模.
3. (还有很多例子但我懒得写了)
]
== 环与模同态
#definition("环同态")[
设 $R, S$ 是两个环, $phi: R -> S$ 是一个映射, 若满足:
1. 对于任意 $a, b in R$, 有 $phi(a + b) = phi(a) + phi(b)$.
2. 对于任意 $a, b in R$, 有 $phi(a b) = phi(a) phi(b)$.
则称 $phi$ 是一个环同态. 若 $R, S$ 都是幺环, 且 $phi(1_R) = 1_S$, 则称 $phi$ 是幺环同态.
]
其他的一些我们所期待的性质都是可以推出的, 例如 $phi(0) = 0$, $phi(-a) = -phi(a)$, $phi(a^n) = phi(a)^n$ 等.
#definition("模同态")[
设 $R$ 是环, $M, N$ 是两个模, $phi: M -> N$ 是一个映射, 若满足:
1. 对于任意 $a, b in M$, 有 $phi(a + b) = phi(a) + phi(b)$.
2. 对于任意 $a in R$, $x in M$, 有 $phi(a x) = a phi(x)$.
则称 $phi$ 是一个模同态.
]
#example[
1. 考虑 $ZZ -> ZZ_m$ 上的一个映射 $a |-> (n mod m)$ 是环同态. 有趣的是不存在环同态 $ZZ_m -> ZZ$. 假设存在, 则 $phi(1) = 1, phi(2) = 2, ..., phi(m) = m$, 但是 $phi(m) = phi(0) = 0$, 矛盾.
2. 1 中的例子不难推广到 $ZZ_(m n) -> ZZ_m$.
3. $R = F[x]$, 对于 $alpha in F$, 定义 $phi(f) = f(alpha)$, 则 $phi$ 是一个环同态.
]
#definition[
设 $phi: R -> S$ 是一个环同态, 则 $ker(phi) = {a in R | phi(a) = 0}$, 称为 $phi$ 的核.
而 $"img" (R) = {phi(a) | a in R}$, 称为 $phi$ 的像.
]
对于模也是一样的, 我们不再赘述.
注意到环的核与像都是在加法与乘法下封闭的, 我们可以从中提炼出子环的概念.
#definition[
设 $R$ 是一个环, $S subset.eq R$, 若满足 $S$ 是 $R$ 的子集, 且对于任意 $a, b in S$, 有 $a + b, a b in S$, 则称 $S$ 是 $R$ 的子环.
]
显然, 对于环同态, 它的核与像是一个子环. 不过核有一个更强的性质: $a in ker(phi), b in R => a b in ker(phi)$, 这是因为 $phi(a b) = phi(a) phi(b) = 0 phi(b) = 0$.
这启示我们子环和子环之间也是不同的. 对于这种子环称为理想.
#definition[
设 $R$ 是一个环, $I subset.eq R$, 若满足 $I$ 是 $R$ 的子集, 且对于任意 $a in I, b in R$, 有 $a b in I$, 则称 $I$ 是 $R$ 的左理想. 右理想类似定义.
]
不难看出, 对于交换环来说 $a R$ 自然构成一个理想, 因为 $a x + a b = a (x + y), a x a y = = a (a x y)$. 这种理想称为由 $a$ 生成的主理想.
#example[
1. $ZZ$ 中的理想都是主理想. 假设 $I$ 是 $ZZ$ 的一个理想, 且 $I != {0}$, 则存在 $m in I, m > 0$ 是最小的, 则 $I = m ZZ$. 若存在 $n > 0$ 不能表示为 $m$ 的倍数, 则根据裴蜀定理, 存在 $x, y in ZZ$ 使得 $m x + n y = gcd(m, n) < m$, 矛盾.
2. 考虑 $R = ZZ(sqrt(-5))$, $I = { a + b sqrt(-5) | a equiv b mod 2 }$, 不难证明 $I$ 是 $R$ 的一个理想. 它不是主理想, 可以视作 $I = "Span" {2, 1 + sqrt(-5)}$.
]
我们知道域有特征的概念, 但当我们考虑环的时候, 这个概念似乎不太好. 以 $ZZ_6$ 为例, 它的特征是 $6$, 然而对于元素 $2$ 来说, $3 dot 2 = 0$, 这似乎是一个特征为 $3$ 的环. 为了解决这个问题, 我们引入了零因子的概念.
#definition[
设 $R$ 是一个环, 若存在 $a, b in R, a != 0, b != 0$, 使得 $a b = 0$, 则称 $a$ 和 $b$ 是 $R$ 中的零因子.
若交换幺环 $R$ 中没有零因子, 则称 $R$ 是一个整环.
]
而在整环上, 特征有了非常好的定义, 我们有下面的定理.
#theorem[
设 $R$ 是一个整环, 若 $a in R, a != 0, m in NN, m a = 0$, 则存在素数 $p$ 使得 $ forall b in R, p b = 0.$
]
#proof[
任取 $b in R$, 考虑 $0 = 0 dot b = (m a) b = a (m b) = 0 => m b = 0$. 找素数与域上的证明类似.
]
== 子环, 理想与商环
上文已经介绍过子环和理想的概念. 我们讨论一些例子.
#example[
1. 所有环同态的 $ker$ 都是理想. (后面会证明所有的理想也都是某一个环同态的 $ker$).
2. $R$ 和 ${0_R}$ 是 $R$ 的理想, 称为平凡理想.
3. 若 $R$ 是幺环, $I$ 是理想, 且 $1_R in I$, 则 $I = R$.
4. 若 $R$ 是域, 则 $R$ 的理想只有 ${0_R}$ 和 $R$ 本身.
5. $R = CC[x]$, 我们证明这也是主理想环. 首先 $CC[x]$ 是一个整环. 假设理想 $I != 0, I != 1$, 假设存在多项式 $P(x) in I, deg p >= 1$. 不妨设 $P$ 在 $I$ 是次数最下的, 这对于任意 $Q(x) in I$, 考虑带余除法 $Q(x) = a(x)P(x) + b(x)$, 其中 $deg b < deg P$, 由理想定义可知 $a(x) P(x) in I => b(x) in I$. 从而 $b = 0$.
6. 考虑 R= $CC[x, y]$ 考虑 $I = x R + y R = {
p in R | p(0, 0) = 0
}$, 这不是主理想.
]
上面的讨论引出了生成的概念.
#definition[
设 $R$ 是一个环, $a in R$, 考虑 $a$ 所生成的理想 $I_a = (a) = {sum_(i=1)^k f_k a g_k | f_k, g_k in R, k in NN}$.
]
#definition[
设环 $R$, $I$ 是 $R$ 的一个理想, 定义 $R$ 上的二元关系 $~_I$: $a ~_I b <=> b - a in I$, 不难验证这是一个等价关系.
在等价类 $R "/" I$ 上定义 $(a + I) + (b + I) := a + b + I$; $(a + I) (b + I) := (a b + I)$. 可以验证这是良定义的, 且构成一个环, 称为 $R$ 关于 $I$ 的商环.
]
不难发现, 考虑 $pi: R -> R "/" I, a |-> a + I$, 则 $pi$ 是一个满射环同态, 且 $ker(pi) = I$.
#example[
1. $QQ(sqrt(2)) = QQ[x] "/" (x^2 - 2)$
2. $CC = RR[x] "/" (x^2 + 1)$
]
== 同态基本定理与中国剩余定理
#theorem("第一同态定理")[
设 $phi: R -> S$ 是一个环同态, 则 $R "/" ker(phi) tilde.equiv "img"(phi)$.
]
#proof[
记 $I = ker(phi)$ 考虑映射 $psi: R "/" I -> "Img"(phi), a + I |-> phi(a)$, 不难验证各种性质...
]
#theorem[
若 $phi: R -> S$ 是满同态, $J = ker(phi)$ 是 $R$ 的理想, 那么
1. 对于 $R$ 中包含 $J$ 的子环 $R'$, 记 $S' = phi(R')$, 则 $S'$ 是 $S$ 的子环; 反之对于 $S$ 的子环 $S'$, 记 $R' = phi^(-1)(S')$, 则 $R'$ 是 $R$ 中包含 $J$ 的子环.
特别的, 上述两条若将 "子环" 换成 "理想" 也成立, 且此时 $R "/" R' tilde.equiv S "/" S'$.
2. 对于每个包含于 $J$ 的 $R$ 的理想 $I$, 存在唯一的环同态 $overline(phi): R "/" I -> S$ 使得 $phi = overline(phi) compose pi_I$, 其中 $pi_I$ 是 $R$ 到 $R "/" I$ 的商同态, 且此时 $ker(overline(phi)) = J "/" I$, 于是 $(R"/" I) "/" (J "/" I) tilde.equiv R "/" J$.
]
#proof[
1. $R'$ 是子环 $=>$ $S' = phi(R')$ 是子环, 容易得到.
2. $S'$ 是子环 $=>$ $R'$ 是子环, 容易得到.
3. $R'$ 是理想 $=>$ $S' = phi(R')$ 是理想. 设 $s_1 in S', s_2 in S$, 要证明 $s_1 s_2 in S'$. 由定义知存在 $r_1 in R' s.t. s_1 = phi(r_1)$, 由满同态知存在 $r_2 in R s.t. s_2 = phi(r_2)$, 则 $s_1 s_2 = phi(r_1) phi(r_2) = phi(r_1 r_2) in S'$.
4. $S'$ 是理想 $=>$ $R'$ 是理想.
5. 要证 $R "/" R' tilde.equiv S "/" S'$, 定义 $psi: a + R' |-> phi(a) + S'$, 良定义不难看出. 容易验证 $psi$ 是单的, 满的, 且为环同态.
定理的第一条证明完毕, 我们回答了对于包含 $ker$ 的子环或者理想的情况.
6. 首先 $I$ 是 $J$ 的理想. 定义 $overline(phi): R "/" I -> S, a + I |-> phi(a)$, 同样不难证明这是良定义的, 满的, 同态.
在验证完 $ker(overline(phi)) = J "/" I$ 后, 由第一同构定理自然有 $R "/" I "/" ker(overline(phi)) tilde.equiv "Img"(overline(phi)) = S tilde.equiv R "/" J$, 这一结论我们称为第三同构定理.
7. $overline(phi)(a+ I) = phi(a) = 0 => a in ker(phi) = J => a + I in J "/" I => ker(overline(phi)) subset.eq J "/" I$. 另一边也是显然的.
8. 最后证明唯一性.
这一部分回答的是被 $ker$ 包含的理想的情况.
]
上面回答了两个理想有包含关系的情况, 下面我们考虑两个理想的和与积, 显然它们都是理想.
#theorem("第二同构定理")[
$phi: I "/" (I sect J) -> (I + J) "/" J$, $x + I sect J |-> x + J$ 是一个环同构.
]
#example[
$R = ZZ, I = 2 ZZ, J = 3 ZZ, I + J = ZZ, I sect J = 6ZZ$, 则 $2ZZ "/" 6 ZZ tilde.equiv ZZ "/" 3 ZZ$.
]
#definition[
设 $I, J$ 是 $R$ 的理想, 若 $I + J = R$, 则称 $I, J$ 互素.
对于幺环, 这一条件等价于 $1_R in I + J$.
]
#theorem("中国剩余定理")[
设 $I, J$ 是 $R$ 的互素理想, 则 $R "/" (I sect J) tilde.equiv (R "/" I) times (R "/" J)$.
]
#proof[
1. 构造 $phi: R -> (R "/" I) times (R "/") J$, $x -> (x + I, x + J)$.
2. 由于 $I + J = R => x = y + z, y in I, z in J$, 所以 $phi(x) = (z + I, y + J)$.
3. 我们要说明 $phi$ 是满的.
4. 不难看出 $ker(phi) = I sect J$. 由环同构第一定理知结论成立.
]
接下来我们将推广到多个理想的情况, 这时我们需要额外的条件.
#definition("理想的乘积")[
设 $I, J$ 是 $R $ 的理想, 定义 $I J = {sum_(i=1)^n a_i b_i | a_i in I, b_i in J, n in NN}$. 这是一个理想.
]
$I J subset.eq I sect J$, 但一般来说不相等. 例如 $R = ZZ, I = 2 ZZ, J = 2 ZZ$, 则 $I J = 4 ZZ, I sect J = 2 ZZ$.
我们关注什么时候 $I J = I sect J$.
#lemma[
设 $R$ 是一个交换幺环, $I_1, ..., I_n$ 是 $R$ 的理想, 且两两互素, 则
1. $I_1 ... I_n = I_1 sect ... sect I_n$.
2. $I_1 + ... + I_(n-1) $ 与 $I_n$ 互素.
]
#proof[
采用数学归纳法.
1. 当 $n=2$ 时 (2) 是显然的. 对于 (1), 显然有 $I_1 I_2 subset.eq I_1 sect I_2$. 考虑 $x in I_1 sect I_2$, 由 $I_1 + I_2 = R$, 所以 $1_R = y + z, y in I_1, z in I_2$. 于是 $x = x 1_R = x y + x z = y x + x z in I_1 I_2$.
2. 当 $n > 2$ 时, $I_n + I_k = R$, 所以 $R = Pi_(k=1)^(n-1) (I_n + I_k) = I_n + I_1 ... I_(n-1) <=> I_n + I_1 sect ... sect I_(n-1) = R$. (1) 同样由归纳假设易得.
]
由这一引理和前面二元版本的中国剩余定理, 我们可以得到多元版本的中国剩余定理.
#theorem("中国剩余定理")[
设 $R$ 是交换幺环, $I_1, ..., I_n$ 是两两互素的理想, 此时有同构 $R slash (I_1 sect ... sect I_n) = (R slash I_1) times ... times (R slash I_n)$
]
#example[
$R = ZZ, I_1 = 3ZZ, I_2 = 5ZZ, I_3 = 7ZZ$, 可以得到 $R slash (I_1 sect I_2 sect I_3) tilde.equiv R slash I_1 times R slash I_2 times R slash I_3$, 即 $ZZ slash 105 ZZ tilde.equiv ZZ slash 3 ZZ times ZZ slash 5 ZZ times ZZ slash 7 ZZ$.
]
== 整环与整除性
环 $supset.eq$ 幺环 $supset.eq$ 交换幺环 $supset.eq$ *整环* $supset.eq$ 整闭整环 $supset.eq$ GCD 环 $supset.eq$ *唯一分解整环* $supset.eq$ *主理想整环* $supset.eq$ *欧几里得整环* $supset.eq$ 域.
我们这里只涉及部分概念.
#definition("整环")[
设 $R$ 是一个非平凡的交换幺环, 若 $R$ 没有零因子, 则称 $R$ 是一个整环.
]
我们知道对于整数环 $ZZ$, 存在有理数域 $QQ supset.eq ZZ$, 一个自然的想法是对于任意整环 $R$, 是否存在域 $F$ 使得 $R supset.eq F$? 这个问题的答案是肯定的.
我们首先定义 $S = R slash {0}$, 显然 $S$ 在乘法下依旧封闭且 $1_R in S$.
下面要构造一个域 $F$, 其中的元素形如 $r / s, r in R, s in S$.
考虑 $(r, s) in R times S$, 定义等价关系 $(r_1, s_1) ~ (r_2, s_2) <=> r_1 s_2 = r_2 s_1$.
考虑 $F = R times S slash ~$, 我们可以在上面定义加法和乘法, 容易验证这是一个域, 我们称为 $R$ 的分式域.
#theorem[
设 $R$ 是一个整环, $F$ 是其分式域, 若有另一个域 $F'$ 以及单的环同态 $phi: R -> F'$, 则存在唯一的域同态 $psi: F -> F'$ 使得 $phi = psi compose i_R$.
换句话说, 分式域是整环的最小域.
]
#definition("素理想")[
设 $R$ 是一个非零交换幺环, $I$ 是 $R$ 的理想, 若 $R slash I$ 是一个整环, 则称 $I$ 是 $R$ 的素理想.
]
#theorem[
$I$ 是素理想 $<=>$ $I != R$ 且对于任意 $a, b in R$, 若 $a b in I$, 则 $a in I$ 或者 $b in I$.
]
#proof[
1.($=>$) $R slash I$ 非零可推出 $I != R$. $a b in I => a b + I = (a + I)(b + I) = 0_(R slash I)$. $R slash I$ 是整环可推出 $a + I =0 or b + I =0$, 即 $a in I or b in I$.
2. 反之, $I != R$ 可推出 $R slash I$ 非零. 考虑 $a + I, b + I in R slash I$, 若 $(a + I)(b + I) = 0$, 则 $a b in I$, 由条件知 $a in I or b in I$, 即 $a + I = 0 or b + I = 0$.
]
#definition("极大理想")[
设 $R$ 是一个非零交换幺环, $m$ 是 $R$ 的理想, 若 $R slash m$ 是一个域, 则称 $m$ 是 $R$ 的极大理想.
]
显然极大理想是素理想. 和素理想一样, 极大理想也有另一种定义方式:
#theorem[
$m$ 是极大理想 $<=>$ $m != R$ 且对于包含 $m$ 的理想只能是 $m$ 或者 $R$.
]
#proof[
1. $=>$ $R slash m$ 是域, 所以 $R slash m$ 的理想只能是 $0$ 或者 $R slash m$, 所以 $R$ 中包含 $m$ 的理想只能是 $m$ 或者 $R$.
2. 若 $R slash m$ 不是域, 则一定存在非平凡的理想, 则 $m$ 一定含于这个非平凡理想, 与条件矛盾.
]
#definition("整除")[
设 $R$ 是一个整环, $a, b in R$, 若存在 $c in R$ 使得 $a = b c$, 则称 $b$ 整除 $a$, 记作 $b | a$.
]
#definition("单位")[
设 $R$ 是一个整环, 若 $a$ 有乘法逆, 则称 $a$ 是一个单位. $R$ 中所有单位构成一个群, 记为 $R^x$.
]
#example[
1. $R = ZZ, R^x = {1, -1}$.
2. $R = ZZ[i], R^x = {1, -1, i, -i}$.
3. $R = ZZ[sqrt(3)]$, 牵扯到 Pell 方程.
]
= 群与群作用
= Galois 理论
|
|
https://github.com/polarkac/MTG-Stories | https://raw.githubusercontent.com/polarkac/MTG-Stories/master/stories/029%20-%20Aether%20Revolt/001_In%20the%20Dead%20of%20Night.typ | typst | #import "@local/mtgstory:0.2.0": conf
#show: doc => conf(
"In the Dead of Night",
set_name: "<NAME>",
story_date: datetime(day: 30, month: 11, year: 2016),
author: "<NAME>",
doc
)
#emph[In an effort to quell a renegade uprising, the Consulate of Ghirapur forcibly confiscated all unapproved devices from the inventors of the city. Access to energy sources was drastically cut, and a mandatory curfew was set in place.]
#emph[Yahenni, an aetherborn socialite and philanthropist, is minutes from death. Desperate for someone to be with them in their passing, Yahenni stumbles through the abandoned streets past curfew in search of the one thing every aetherborn is supposed to be guaranteed: a party before they die.]
#v(0.35em)
#line(length: 100%, stroke: rgb(90%, 90%, 90%))
#v(0.35em)
#strong[I]
#figure(image("001_In the Dead of Night/01.jpg", width: 100%), caption: [Art by <NAME> Ro], supplement: none, numbering: none)
I need #emph[someone] to be with me when I die. I need a hand to hold what is left of my shoulder together. I need someone to witness the fact that I existed and then did not. A caring voice to whisper "You're safe. It's okay, Yahenni, let go when you're ready." I need anyone. #emph[Anyone] .
I'll find someone else if it kills me.
It is dark and I am the only person shambling under the eaves of the Weldfast. The thoroughfare is empty, the stalls closed and abandoned. There are no lights to keep me company save those emitted by my own body. No inventors (Emergency Ordinance #89-A), no aether (Emergency Ordinance #89-B), and here I am like a drunk bandar searching vainly for someone to celebrate with me while I die. I had been confined to my penthouse for too long, and with Emergency Ordinance #89-C in effect, certainly no one was going to come to me.
I can sense only one other being on this street: A starving gremlin lies under a cruiser parked to my left, pupils wide in the night and belly sunken with hunger. It's been following me for the last twenty minutes. I look away. We both smell of death.
Every aetherborn deserves a Penultimate Party, but no one celebrates anything these days.
I feel the back of my left hand burst in a cloud of dissipating aether. It's a calming release that eases the tension. The rest of my body yearns to escape with it. It would be so easy.
I trip over a piece of crushed delivery servo. Part of my foot is left behind with it. I hear the stalking gremlin scurry toward it and feast on the meager bits of myself that are left behind on the shell of the servo. There's a common warning among aetherborn: gremlins won't hunt, but they will gladly wait.
I stumble on. I have fifteen minutes left.
What was I before I lived, I wonder? Did I spend my eternities floating through the Conduit? Did I power cities? Feed gremlins? What mundane forever awaits me when I die—
It hits me at once. A train that arrives in a silent crash.
I'm going to die alone.
My panic causes me to stumble faster. Toward where, I have no idea. If I open my senses (which, oddly enough, have never been more acute—thumbs up for necrosis!) I can sense people hiding in their apartments. All of them are sour with unease. Spread out and secluded. What used to be the best night district in the city is boarded up, shut down, barred closed in accordance with the citywide curfew. The only sound on these streets is the patter of my footsteps as I stumble searching for any sign of a gathering. No curfew will keep me from my birthright. I earned a final celebration, and I will find it if it kills me.
I look behind me to that gremlin. It looks back in hunger. I start to panic.
It's actually happening. I'm going to die alone.
I'm going to die alone.
I'm going to die alone.
I hold my more complete hand against a building to balance myself and begin to stumble faster. My dermis is loosely containing me...I'm held together by clinging bits of smoke and crumbling ash. I halt myself and focus my senses. In the distance I can smell the wet wool of despair, mineral-tinged determination, resilient tamarind—
Wait! I know that tamarind!
I stumble toward the empathic scent. It's a few blocks away.
#v(0.35em)
#line(length: 100%, stroke: rgb(90%, 90%, 90%))
#v(0.35em)
#strong[II]
As I've grown older, I've slowly become more and more aware of the exactness of time I have left. I imagine it's the same sense that tells beings with organs and junk when they need to eat or if they have the flu or when they need to pee. When I was a few weeks old, I knew I had something like four years left. When I was a year old, I knew I had about three years and a month. And a while ago, I knew I had exactly twenty-two days. I now know I have twelve minutes left. I know and it is terrifying.
The scent of tamarind grows stronger. I can see the walls of the Museum of Invention up ahead. It's been coated with dozens of Consulate banners in the last few weeks, but square on the front of the building is a bare patch where the banners had been ripped down. In its place is...something. I move closer, and through the dark I make out fresh paint glimmering in the starlight.
#figure(image("001_In the Dead of Night/02.jpg", width: 100%), caption: [Spontaneous Artist | Art by <NAME>], supplement: none, numbering: none)
I recognize it as the symbol of the renegades—an upside down Consulate symbol with elaborate flourishes emptying out of the bottom. They call it the leaking spire. A symbol of hope that aether is meant to be returned to the people.
From across the street I can make out a human figure putting the final touches on their graffiti.
My heart sings—I know this person! It's Nived, my favorite caterer!
Ahhh, #emph[Nived] ! What a guy! I haven't seen him since my party before the Inventors' Fair! Extravagant buffets, intimate catered meals...there's nothing Nived can't cook for. I had booked him for my Penultimate...
A wave of sadness rushes over me. With everything being as it is, I had to cancel my own Penultimate Party. #emph[I had to cancel my own Penultimate Party] .
"Nived!" I scream-whisper from nearby. Nived jumps and looks at me with eyes wide. His face is painted and a jerry-rigged meat-cleaver-arm apparatus is strapped to his wrist. I'm delighted. Look at my friend, the hooligan!
He puts a finger to his lips. Shh. Freak out later. I wheeze and stumble closer. Seven minutes left. My legs give way as I reach Nived. My voice is wavering. Talking is difficult, but this is deeply important. This may well be the last being I ever encounter and it is time to atone while I can.
"Yahenni? Is that you?" he asks while rapidly packing up the last of his paint. He kneels down to my place on the ground.
"What's left of me," I pathetically kid. "Glad to see you doing your civic duty."
"Your #emph[body] , what's—"
"I don't have long. Nived...I wanted to apologize, darling."
"What do you have to apologize for?!"
The tide of anguish washes back over me. I have so little time left. I need to make my words count. I place my hand on Nived's shoulder.
"I'm sorry...I canceled...less than a day prior to when my party was scheduled..."
"...Are you serious?"
My body shivers in weakness and frustration. "I'm dying! Of course I'm serious!"
"You are ridiculous—"
"I'm very respectful of cancellation policies."
Suddenly our space is flooded with empathic stench.
"HOLD IT RIGHT THERE!" shouts an authoritative voice from around the corner.
How did I not sense them?! A massive Consulate enforcer ("The Honorable" my ass!) rounds the corner of the Museum alongside an armament automaton. Their eyes are locked squarely on Nived. "You are under arrest for defacement and vandalism!"
#figure(image("001_In the Dead of Night/03.jpg", width: 100%), caption: [Art by <NAME>], supplement: none, numbering: none)
Nived tries to bolt, but the enforcer throws a device at his shoulders. From above, four spheres lower from nearby rails and emit a brilliant blue spark of energy. Nived screams, seizes, and topples to the ground.
"NIVED!"
I feel a sudden sob escape me. My body—Nived's body?—My body?—#emph[hurts] with a stinging pain and my heart fills with acrid fear. Physical smoke floats away from my friend's singed clothes. #emph[My empathy may kill me] , I think distantly through the haze my friend's (my own?) terror.
Ignoring my cries, the Consulate enforcer walks over and stands over the body. I catch the enforcer and their psychic scent. Their presence is like standing near a deep crevasse. A sudden awareness of absence. This enforcer standing over the body of my friend (the best caterer in Ghirapur, #emph[you bastard] ) is an empty well, filled only with a distant scent of sadism and shining brass. I am too weak to run, and the fear of my friend is drenching my senses.
The scent of brass warms with dark curiosity. I wish I could vomit. I wish I could purge the stink of this person's heart from my insides and spew it on the ground.
I see Nived move slightly, and the enforcer hits the energy device again.
Everything smells of terror and morbid pleasure and I can't do anything.
Nived tries to move.
No one is here to help. We're alone.
The enforcer activates the device again. The vivid lights of dangerous aether arc toward my friend's body. Nived is completely still.
"Leave him alone," I weakly assert.
The enforcer doesn't move. It's too dark to see, but I feel them languidly smile. They zap the unconscious body again.
"Stop it! You'll kill him!"
I heave myself up with all of my strength and attempt to rush the enforcer, but stumble to the ground. I'm too close to my own death (three minutes). The enforcer turns and looks down on me. I am a handspan away, smoking, crumbling, falling apart.
The enforcer kneels down to my level. The glow of my escaping aether lights up the cruel lines of their face from below, distorting the planes of their empty smile. "You're that Yahenni...right? Seen your picture in a press report." I shiver. "I'm looking for six individuals that are sympathetic to the renegades' cause. One is the daughter of the criminal Pia Nalaar."
My head spins. I met this daughter...Chandra was her name? I saw her only a few weeks ago. What had she and Nissa done to warrant this much Consulate attention in that short time, I wonder.
The enforcer stands to their full height and sneers, "I'll finish off this scum here if you don't tell me what you know." They kick Nived's unmoving body.
I bristle.
The Enforcer kicks him again, "What's one unconscious renegade to you, weakling?"
Pulling from the last bit of strength I have, I rise up. My leg shivers on my one remaining foot and my right hand itches in fury. I look the Consulate enforcer in the eye and whisper with my dying breath—
"He's my caterer."
#figure(image("001_In the Dead of Night/04.jpg", width: 100%), caption: [Art by <NAME>], supplement: none, numbering: none)
Without planning, without a second thought, without consideration to the conscience at the back of my mind, I claw my right hand and #emph[pull ] from the enforcer's neck. The brilliant light of essence leaks from their skin and into the grip of my hand.
The Consulate enforcer screams, and the exhilaration I feel is matched by a boundless wave of pain.
I can't help the cry that bursts out of me in tandem with them. #emph[I feel everything the enforcer feels.] They are dying and it feels like #emph[I ] am dying and it hurts and it is miserable and I am simultaneously both killer and killed.
Through the enforcer's screams, I remember the vengeful cruelty they relished only moments before.
I need to finish this if I'm going to survive.
After an endless seven seconds, I open my hand and the consulate enforcer falls to the ground. Their lifeless body lies beside Nived's unconscious one.
My everything is tingling. A bubble of panicky post-pain anxiety rises within me. Why did that hurt?! Why did I feel everything that this awful enforcer felt as they died?! When I drained essence the first time I only felt the pleasure of #emph[life,] why would this be different?
The answer settles a leaden weight in my mind. The first time I drained something's essence it wasn't a #emph[person] . Today I killed a #emph[person] .
...I am a murderer.
The thought feels distant. It's overshadowed by what has happened to me physically. My body feels strangely...glutted. Pleasantly stuffed. I have two hands. I have two feet. I stand at full height and stretch. The gaps are filled, and my dermis feels slightly more complete. The urgency feels relieved. I'm...full? I think? I take stock of how much of my time is left.
Twelve entire days.
Oh.
I have bloated several minutes into twelve days at the cost of a life. I did what I had to do to survive. I killed to save myself. Didn't I?
A noise brings me back to the present. Reaching out I feel people moving quickly toward us—the enforcer's backup must have overheard. I scoop up Nived's body and hide him safely behind a nearby empty stall. Hidden by the barricade, my mind lurches from thought to thought.
What if I don't have to die? What if this is the solution I desperately needed? I need to lean in. I need to be calm and I need to not #emph[worry] about this and I need to accept that if I'm going to kill to survive, I may as well kill the bad people.
...But if that is the rule I choose to live by, then I myself deserve to die.
A private whimper escapes me.
I can't allow myself to be weak. Not now, when I've found a way to cheat the inevitability of death. I am sick of waiting for that awful train to arrive and take me away.
I have twelve days! I can do so much in twelve days!
But if I want to do something with those twelve days, I need to find the people whom I can proudly fight alongside. If I work with them and kill the bad guys, then that would negate my crimes in the eyes of my peers, wouldn't it?
The lie comforts me. My mind is set. I need to find the renegades. I need to find the daughter of a criminal. I need to find the elf with endless eyes.
There is only one person in this city who knows more about its hiding places than I do.
Gonti.
#v(0.35em)
#line(length: 100%, stroke: rgb(90%, 90%, 90%))
#v(0.35em)
#figure(image("001_In the Dead of Night/05.jpg", width: 100%), caption: [Gonti, Lord of Luxury | Art by Daarken], supplement: none, numbering: none)
#strong[III]
After getting Nived's unconscious body back to my penthouse, it takes a full hour of enforcer-dodging, alley-sneaking, and stair-descending to reach the private residence of the infamous crime lord Gonti. We aetherborn are vain as a necessity, but Gonti's vanity knows no price tag.
Through the grace of my minor celebrity (if you ever want to be popular, get rich and donate most of your money to people with sad stories; then tell the news about it), I am let into the hideout without much conflict. This residence is essentially a palace disguised on the outside as a warehouse. The security at the door nod their head at my request to speak to Gonti, and they agree to lead me to them.
As we walk I can't help but gape at the sheer #emph[wealth] of the place. I would normally call it tacky, but honestly, this level of pompous cash-flinging is a thing to be respected. Gonti's residence is a marvel of stolen opulence; bedazzled filigree, embezzled decor. I enter a vast entry hall, at the end of which is a boardroom table, and between me and it is massive room of plush carpet and luxurious couches. Reclining on the couches are a mix of recent renegades and old-timers of the crime syndicate. They sip tea and trade secrets while their eyes follow me as I am escorted through the hall. An automaton delivers food and comforts to the guests all the while. If there were ever a place to be stuck during a curfew, this would be it.
I am walked in through this entry hall past the scattered rogues and ne'er-do-wells and brought through a glittering set of doors. This room is painted to look like a pastoral paradise—leafy trees and meandering streams, a mural of the Great Conduit winks down from the ceiling above. Glittery pens line the walls, and inside the cages is a small petting zoo of animal constructs. A mechanical fox and filigree deer playfully prance on thick rugs nearby. Ugh. I despise purposefully eccentric interior design. Try as some might, you #emph[just ] #emph[can't] mask boring taste. Through the next set of doors is a dazzling acrobat practicing poses while dangling from the ceiling, and through another door from there is an endless apothecary of the finest aether attars. The connecting halls are lined with cabinet after cabinet of shimmering devices without a mass-production seal in sight. All secret, all stolen, all safe from the Consulate's eager hand.
At the end of this lavish maze is a foggy glass door. The security stands to the side and motions me to walk through the door. As I do, a waft of steam washes over me and I realize I am standing in front of a large, deep pool of warm water; a bath of what smells like jasmine aether attar. The walls are pounded copper, and my reflection is infinitely and hazily echoed by the glow of myself and the aetherborn seated in the water before me.
Gonti sits submerged, their face covered with a gilded mask. At the center of their chest is a curious metal lump.
#figure(image("001_In the Dead of Night/06.jpg", width: 100%), caption: [Art by <NAME>], supplement: none, numbering: none)
Odd. I don't think I was supposed to see that.
My mind whirls as Gonti gives off a burst of empathic surprise and quickly rises. Baths are not unheard of for our kind...but one gauzy with the glow of stolen aether certainly is. I wonder what it would be like to relax after a long days' work in a tub full of the same stuff I'm made of. It must have the wonderful yet temporary kick that a dose of aether attar will give...but for the entire body. No wonder Gonti stays rich. It must take a lot of crime syndicate funds to maintain #emph[that ] habit.
As I internally muse, Gonti covers up in an exquisitely soft-looking black robe.
I imagine conversations between healthy aetherborn must seem fast by organic standards. An innate empathic understanding leads to discussions being more about why someone is feeling something versus how. Little time is wasted, and language isn't terribly poetic. Poetry is for people who have to explain what they can't say.
Gonti straightens their robe and tilts their head.
"You smell of guilt. It reeks."
Damn. I thought I was doing a good job hiding it. Cards on the table, I suppose. "The Consulate pushed me to my limit, darling, and this is the result."
Gonti leads me into what looks like a more private version of the plush-carpet-and-couch room I came through initially. I read them as they observe my own emotional state. They're considering my air of curiosity and weighing if it's worth it to inquire further. In an instant, I feel Gonti tilt toward dismissiveness. "If you are looking for protection I cannot offer it. I have enough trivialities and trifles that eat at my time."
"I'm looking for something that would help both of us," I say, projecting earnestness.
Gonti is intrigued at that. They cross the room to a large couch in front of a beautiful statue. The art piece nestled on a stand behind them seems to be made of the sky itself. I don't want to know how valuable it might be. They sit gracefully on a couch in front of the impressive object.
On the surface Gonti's scent is impatient, mildly frustrated, but underneath lies a base scent of desperation. Sour anxiety. The scent finishes on a note of dread.
Their train must be arriving, too. I wonder how that shiny new heart works.
I project tentative graciousness. A tang of mischievous coriander.
"You seek rebellion?" Gonti asks.
"I seek the humans Chandra and <NAME>."
Some aetherborn are gifted at lying. I feel as Gonti floods their aura with a haze of grassy ambivalence to prevent a surface emotional reading. They don't trust me. I respond with a breeze of camaraderie and violets, "We are helping each other if we help them. Besides..."
I lean in and speak quietly enough the security outside won't hear.
"If you tell me where they are hiding, I will keep the secret of your manufactured heart to myself. Certainly wouldn't want the Consulate confiscating that."
The grassy ambivalence evaporates into alarmed, acidic pepper and a distant disappointment in foolish security guards.
I project overwhelming trust with an undercurrent of jealousy. Gonti responds with a nod and dal-scented self-satisfaction.
That jealousy I put forward can dog-whistle my secret. I feel Gonti now calculating how much more of my dermis I have compared to when they must have seen me in the press reports last. They give a sudden burst of surprise as they realize what I can do.
"Essence drainers are rare," Gonti replies, "I've only ever had two in my employment. How did you discover it?"
"On my own. Not all of us are lucky enough to have built our own hearts."
I don't care if they sense my lie. I was four weeks old. A dwarven friend of mine brought a hyena to a party...I petted the creature and it just happened (It was an accident. It really was. Depala understood and she forgave me all the same.)
"Quit dwelling, Yahenni. How does it feel #emph[when] you do it?"
The question halts me. After the incident with the enforcer, I recognize now that Depala's pet was an anomaly. It is a very different thing to kill a person. I can feel their death, for one thing. But it also feels like when I introduce an up-and-comer to the person who will change their life. It feels like when my friends dance for hours under the stars. It feels like my business partner closing a deal, it feels like rich rose-scented elation and the grateful cinnamon glow of a young researcher receiving a much-needed grant from me. It feels like the lightning strike of two future lovers looking at each other from across a crowded room.
It feels as if all of that...and it also feels like unparalleled suffering. The shock of my own birth. Depala's scream as I accidentally killed her beloved pet. My firm losing more money in one night than most see in a lifetime. Empathically experiencing my neighbor's depression through the wall our houses shared. The grief of being young and not understanding why Farhal, Vedi, Dhriti, Najm, all of my aetherborn family kept dying and dying—
My two seconds of musing is interrupted by a scoff. "No wonder you stink of guilt," Gonti chides.
"My inner life is none of your business."
I'm met with a slap of charmed amusement. Honey and cashews—how quaint they think I am.
"If you feel like killing again, you may be of use to our city. With the curfew in place and the restrictions on aether imposed, my employees are deeply hindered in their ability to continue business. We innovate, of course, but the fact remains that the Consulate's mandatory curfew and confiscation of our personal property is a curse on our city. Ghirapur needs the renegades to make a collective move. I will tell you where Nalaar is and you will warn her and her renegades that I'm sending the Consulate to their hideout."
I sit up straight. "Why?!—"
I'm met with dominant and offended agarwood, "They need to be urged into action. Give them a warning to force them into making a move against the Consulate. If they attack first, then fewer of my fighters have to die."
I back off with hushed compliance. You don't become a crime lord by being bad at bargaining.
"You'll find the younger Nalaar and her associates in a safe house within the Statuary Garden. Tell them they are unsafe. Frighten them into action. You are a monster now, so frightening people should be second nature. #emph[Do] try not to drain them, Yahenni."
Our conversation lasted all of two minutes.
#v(0.35em)
#line(length: 100%, stroke: rgb(90%, 90%, 90%))
#v(0.35em)
#figure(image("001_In the Dead of Night/07.jpg", width: 100%), caption: [Art by <NAME>l], supplement: none, numbering: none)
#strong[IV]
The following day I walk purposefully to the Statuary Garden to find Nalaar's hideout. Moving in the daytime is easier than sneaking around at night, but the presence of the Consulate is still stifling. No one lingers on the streets, and the pace of life is even more hurried than before. The journey from my penthouse to the Statuary Garden is rushed and quiet. If Chandra and Nissa (and company) have done enough to upset the Consulate, then they must be worth helping. May as well spend the remainder of my days being helpful.
The Statuary Garden is a massive arboretum near Aradara Station. Two dozen huge statues of graceful curved metal line the walkway, each representing Ghirapur's most famous inventors. The tradition of immortalizing inventors started with the Aradaras themselves—the mother-and-son team who perfected the aether-propelled train. To have a statue here is the highest honor an inventor can achieve. The Aradaras created their train only shortly after the aether boom, and the statues of those who discovered the aether refining process stand near behind them in the garden. I'm oddly touched as I watch the sun shine weakly through the thin clouds on the faces of the people who inadvertently caused the creation of my race.
It's strange; since nearing my expiration date, my senses have increased tenfold. The ebb and flow of emotion is like walking through a museum. The art is plainly laid out and easy to spot from afar. I use my senses to try and locate the hiding places of my friends. From high up an immense statue of a Vedalken inventor, I feel a shimmer of anxiety and uncertainty. It must be them.
I walk casually toward the statue and start to climb a ladder around the back. This thing is huge. I find myself wondering why I never built something this tall when I was employed.
A clunking noise. I freeze. A repurposed security automaton is patrolling through the garden toward the station. Stupid no-emotion-having hunk of garbage scared the aether out of me. I'm fairly confident the machine doesn't notice me and I climb upward.
As I ascend I do an internal check. Eleven days are left. How much time do I gain with each life that I steal? Is it safe if I only do it to the Consulate? Will I have enough time to do enough good once all this is over?
I'm hit with an excruciating body ache. The force of it nearly causes my hands to let go, but I'm #emph[so] close to the hatch near the top. I hear just above me:
"There's something coming up the ladder that doesn't have a brain."
Rude.
The voice comes from a person who feels of rain on stone and a lot of unanswered questions. "I've never read anything like this before…I think they know you two?" The person sounds masculine and is in the compartment above speaking to someone I also can't see. The pain of whatever is happening to me halts my progress upward.
"Open the hatch, dammit!" A feminine voice. Is that...marigolds...?
The curious petrichor person continues, "Whoever it is was sent here from a crime lord."
"I believe it would be best if we listened to what they had to say." I know that scent! Neroli! It's Nissa!
"Nissa! It's Yahenni!" I yell through the pain of whatever the petrichor person is doing to me.
I hear a scuffle above. My body ache vanishes and I hear the rain-scented one again. "Chandra, let them in."
"Yahenni!" Chandra yells while opening the hatch and pulling me through. The space at the top of the statue is strangely sizeable. There are five cots stacked in the corner and a pile of cushions on the floor as a makeshift bed-nest. A bag of gear lays in the corner, and a wooden staff rests on top.
A stranger in an even stranger cloak looks me over as I climb inside, their mind buzzing with curiosity. I actively decide they are well-dressed but nosy.
I wave a little. "Hello Nissa, hello Chandra."
The elf smiles. She's just as alarmingly pretty as I remember. Chandra stands nearby and waves in return. "Hey, Yahenni. Thanks for the party before."
"Happy to have you there. I heard you found your parent."
"Yeah, we got her free. She's meeting with some other renegades now."
I shake my head, "Shame she had to deal with that Tezzeret fellow. He's dreadful."
"He's a tool," Chandra spits.
"You can swear in front of me, darling, I won't tell your mother." Chandra smiles at that.
I see behind her two other humans—a human in a dark dress (is that fur on the edge of the collar? How barbaric. Who does that?) sitting relaxed but irritated in a chair, and a beefy, sideburn-laden human watching the outside through a gap in the walls.
"This is Yahenni. They're someone we can trust," Chandra says as an introduction to the group. I lift my head in grateful pride. "Yahenni, this man is Jace, this woman is Liliana, and the man in the corner is Gideon."
"Strange friends you have here," I jest.
"If you think we're weird, wait 'til you see the giant cat," Chandra says.
"...Cat?"
"He's with Mrs. Pashiri at the receiving line for our grocery rations," Nissa says plainly.
"I see."
I don't.
"There isn't time," I divert, "all of you need to leave. The Consulate is on their way to this location if you don't scram."
The energy in the room fills with alertness. The four humans and singular elf all share a quick glance with one another. While alert, there is no sense of fear in their scents. Only preparedness.
"If they're coming we should be ready to fight," Nissa says resolutely.
"We should decide #emph[if ] we want a fight first." Jace adds.
"Tezzeret might be with them," the woman in the dark dress states grimly.
"It's not the kind of fight that you win," I say with resolution.
The scent of the group immediately splits. A resolute cumin. An internal groan of annoyance. An anxious but confident rotting corpse (wait, what?).
"Why did a crime lord send you to us?" the man named Jace asks me.
How did he know that? "Gonti is the only person in this city that knows more hiding places than I do, so I went to them to find out your location. I want to join the renegade cause, and I knew if I found you all you could make it happen."
The tenseness of the group isn't going away. We'll have to do this differently.
"My penthouse is safe. There are enough security measures to keep you all unnoticed. I'll take you there tonight, and you can discuss your involvement from there. Neither Gonti nor the Consulate will know you're going with me."
"We can trust Yahenni," Nissa says, solid and firm.
The other group shares a quick glance. Gideon nods, and the rest begin to pack up. The woman in the dark dress slinks up from the bed and looks me over.
"Does your penthouse have more than five bedrooms?" she asks. The woman smells of damp topsoil and an admirably healthy ego.
"Darling, I wouldn't sleep in a house with fewer than seven," I respond. She nods in appreciation and holds out a hand.
"Pleasure to meet you, Yahenni," she says.
I shake her hand, "Happy to be of service, darling."
I empathically reach out to the area past the statue.
"I'll go down the ladder first," I say. "Follow me."
I open the hatch and descend the ladder. I feel the others follow behind me.
The wind whips my cape. In my malaise yesterday (pre-draining), I had chosen it as my dying outfit. I feel the newly-stolen life course through my being, and my mood catches on sentiment. I warm with bittersweet pleasure. I get to wear this cape again after all.
It's a long way down. The statuary garden is quiet. The birds that normally roost here are absent; the crowds that normally fill the walkways are gone.
It's eerie here in the shadow of these inventors. On my way down the ladder, I see the outline of the statue of the great aetherborn inventor Rajul in the distance. They pioneered some of the first medical technology for non-organic beings. Rajul remains an inspiration. It has always given me comfort to see them standing alongside the greatest names of our time. I am thankful that my kind has never been treated as separate from the rest of the city that birthed us. The great looming statue of Rajul is a bold affirmation of our belonging. They did just what every other inventor in here did...and #emph[they] did it when they were two years old.
I am a few body lengths from the ground and feel the others above me discussing and beginning to descend, but my other senses are caught by a sudden drone of noise in the distance that turns my head. I grip the ladder tight and look where the noise is coming from.
My nostalgia transforms into fear.
The roar of an engine is quickly approaching. I see a single Consulate cruiser round the corner through the gardens and accelerate toward our statue. I tense in alarm. The vehicle veers off the main road and barrels across the grass. What are they doing?! The curfew isn't until later, we're safe!
Unless Gonti already tipped off the enforcers. If they did, then we are truly screwed. The speed and direction of the cruiser makes it painfully clear that Gonti doesn't wait for anything after all. The Consulate is coming right for the ladder.
I definitely cannot outrun a Consulate cruiser if I get to the ground.
We'll be trapped in the statue if we all go back up.
I don't have time to weigh moral options.
The car is pointed at the ladder to the statue (does this enforcer intend to ram us down?!)
I turn my entire body around, feet pointed out, left hand gripping the rung (what in the world am I doing).
This is a bad idea. (This is the worst idea—I haven't done anything vaguely athletic in my life.)
I claw my right hand and feel a now-familiar pull in my palm (I'm going to feel them die, I'm going to #emph[feel ] them #emph[die] #strong[but I don't have any other options] #strong[.] )
And I jump down.
And I land on the hood of the vehicle.
#figure(image("001_In the Dead of Night/08.jpg", width: 100%), caption: [Art by <NAME>], supplement: none, numbering: none)
Several seconds of anguish.
Several seconds of ecstasy.
Their pain is mine and my elation is mine and it feels like I'm drowning.
It takes significant effort, but I don't cry out loud this time.
The vehicle swerves out of the way of our statue as the Consulate enforcer falls dead on the wheel.
I tuck and roll off of the car.
I hear a crash as it rams into one of the other monuments.
Take a moment. Am I alive? I'm alive. I'm alive and I killed #emph[two people in the same day ] and what are people going to #emph[think] of me—
Oh.
I now have twenty-two days left to live.
Amazing. Abhorrent. I'm not quite sure who I am anymore.
"Yahenni! What happened, are you all right?!" a feminine marigold voice calls from nearby. They must have all made it down. I turn to see three humans and an elf staring shocked and concerned at me while the woman in the violet dress somehow manages to gracefully descend the ladder in heels.
The vehicle is crumpled up against the side of the other nearby statue. The enforcer I killed is hanging still and pathetic out of the side. My hands start to shake, and I realize in a corner of my mind that the others with me aren't even remotely fazed by what happened. This is nothing. They've seen worse.
I want to scream.
I want to sob.
I want to go home.
"It's all right, I'm fine." My voice breaks as I reply.
The others ease up as they take stock and quickly refocus.
Chandra nods, turns, and starts walking away with purpose.
Nissa looks from her to me and then runs to help me up.
She looks in the direction Chandra went off in. "I don't think Chandra actually knows where she's going, she just started walking."
I stand and straighten myself out. Shake out my cape.
"Gideon, can you call Chandra for me, please," Nissa says in typical softness to Gideon.
He cups his hands and yells, "WRONG WAY, CHANDRA!"
The redhead in the distance stops and about-turns back toward us. I watch as Nissa closes her eyes briefly and points in the opposite direction Chandra had been walking.
"Tell <NAME>'s home is that way, and have Jace inform Ajani, Pia, and Mrs. Pashiri of our new location," she casually instructs. Gideon nods and walks away from us to inform the others.
I'm left with Nissa.
She lifts me easily and looks on with anxiety. "Are you hurt?"
"Physically, no."
Emotionally? I feel damaged without repair. Nissa is looking at me with tender sympathy...but under her concern is a small ember of surprise. I feel her subconsciously stamp it out. Below the level of her own perception, did she not expect me to be upset after killing someone...?
Her brow is furrowed in honest copper worry.
"Tell me what I can do to help."
I want to shrug, but instead I stand in silent distress. That ember I sensed is dead, extinguished with a flood of Nissa's own empathy. The elf moves toward me, her shoulders falling in compassion. "Yahenni, you have suffered enough."
She closes her eyes.
I feel a distant, tuneless song. A current of energy is delicately lifted from somewhere beneath me—is Nissa doing that?—and channeled into somewhere near my shoulder. I feel a reassuring stream of my own city's vibrancy pass into me, comforting and pleasant. It doesn't heal, but it helps. A reminder that I am part of a much greater whole.
"I killed two people today, Nissa. I didn't have a choice; they were both going to kill me first. I—" My voice breaks, "I don't want to drain again. When I do it, I feel...everything."
The warm energy passing from the elf to my shoulder feels lovely. I stifle a sob.
"You must think so little of me now," I say more to myself than her. "How can you stand to go to a murderer's house to hide?"
"Because you are my friend," she says delicately. It's quiet, but her mood is picking around the phrase like a bird at a seed. Testing. Touching, deciding, landing at resolution.
Merciful neroli fills the space between us. I pause to decipher the meaning and sense what Nissa is trying to say.
...She has also made mistakes.
I look to the four humans walking our way. They're good people. Maybe they have regrets too.
The gentle energy continues to warm my shoulder. Her kindness allows a thought to bloom in my mind, and I understand it clearly. #emph[These people are like me] #emph[.]
I will certainly be forced to kill again as they will certainly be forced by responsibility to harm as well. But these people, these renegades...in the end, they help more than they harm. Our suffering is inevitable, but like these strangers, I possess tremendous power to create more good than bad in the world. And when I act on that, in return, won't it #emph[feel] #strong[amazing] ?
I think of my own future death.
I have twenty-two days left to live.
I can do so much in twenty-two days. What a #emph[wonderfully] long life to live.
Nissa's presence is a canopy of orange blossoms.
"Thank you, Nissa."
"You're welcome, Yahenni."
I turn to the others and wave them over as the sweet little river of energy fades back into the land beneath me. "This way to my place."
|
|
https://github.com/Ajsoabk/Exam-Paper-Answer-and-Analysis-typst-template | https://raw.githubusercontent.com/Ajsoabk/Exam-Paper-Answer-and-Analysis-typst-template/main/exam_paper_answer.typ | typst |
#set page(
paper: "a6",
margin: (x: 1.8cm, y: 1.5cm),
)
#let conf(title:"",affiliation:"",body)={
set page(
paper:"a4",
margin:2.5cm,
background:
rotate(24deg,text(18pt, fill: rgb("FFCBC4"))[*#affiliation*])
);
align(center,text(size: 24pt,weight: "bold")[#title])
body
}
#let answer_table(anss)={
table(columns: anss.len(),..range(1,anss.len()+1).map(str),..anss)
}
/**
选择题与判断题的输出，包括题面，选项*，代码*
*/
#let limited_selection_problem(statement,opts,code,statement_size,answer,analysis)={
text(size:statement_size)[#statement]//题面
if code!=none{
raw(code,block: true,lang: "c++")
}
else{parbreak()}
let opt_cnt = counter("option_counter")
opt_cnt.update(0)
for opt in opts{
opt_cnt.step();
text(size:12pt)[☐ #opt_cnt.display("A"). #opt\ ]
}
parbreak()
text([【答案】#answer\ 【解析】#analysis\ ],fill: red)
}
#let selection(body,opts,answer,analysis,code:none)={
let cnt = counter("selection_problem_counter")
cnt.step();
limited_selection_problem(
[#cnt.display().#body],
opts,
code,
15pt,
answer.last(),
analysis)
}
#let judgement(body,answer,analysis)={
let cnt = counter("judgement_problem_counter")
cnt.step();
limited_selection_problem(
[#cnt.display().#body ( )],
(),
none,
12pt,
if answer.last()==true{"√"}else{"x"},
analysis)
}
|
|
https://github.com/f14-bertolotti/bedlam | https://raw.githubusercontent.com/f14-bertolotti/bedlam/main/src/measure-theory/main.typ | typst | = Measure Theory
#include "introduction.typ"
#include "caratheodory-extension-theorem.typ"
#include "lebesgue-measure.typ"
|
|
https://github.com/gongke6642/tuling | https://raw.githubusercontent.com/gongke6642/tuling/main/Math/leftright.typ | typst | #set text(
size:10pt,
)
#set page(
paper:"a5",
margin:(x:1.8cm,y:1.5cm),
)
#set par(
justify: true,
leading: 0.52em,
)
= 左/右
分隔符匹配。
lr函数允许您匹配两个分隔符，并使用它们包含的内容进行缩放。虽然对于语法匹配的分隔符也会自动发生这种情况，但lr允许您匹配两个任意分隔符并精确控制它们的大小。除了lr函数之外，Typst 还提供了更多函数，用于为绝对值、水解值和下限值以及范数创建分隔符配对。
= 例
#image("26.png")
= 功能
= lr
缩放分隔符。
虽然默认情况下匹配的分隔符缩放，但这可用于缩放不匹配的分隔符，并更精确地控制分隔符缩放。
#image("27.png")
= 大小
括号的大小，相对于包装内容的高度。
默认：auto
= 内容
分隔的内容，包括分隔符。
= 中
将分隔符垂直缩放到最近周围的 lr() 组。
#image("28.png")
= 内容
要缩放的内容。
= 绝对值
采用表达式的绝对值。
#image("29.png")
= 大小
括号的大小，相对于包装内容的高度。
= 内容
取绝对值的表达式。
= 模方
采用表达式的模方。
#image("30.png")
= 大小
括号的大小，相对于包装内容的高度。
= 内容
采取模方的表达式。
= 向下取整
向下取整表达式
#image("31.png")
= 大小
括号的大小，相对于包装内容的高度。
= 内容
采取向下取整的表达式。
= 向上取整
向上取整表达式
#image("32.png")
= 大小
括号的大小，相对于包装内容的高度。
= 内容
采取向上取整的表达式。
= 四舍五入
对表达式进行四舍五入。
#image("33.png")
= 大小
括号的大小，相对于包装内容的高度。
= 内容
采取四舍五入的表达式。 |
|
https://github.com/rabotaem-incorporated/algebra-conspect-1course | https://raw.githubusercontent.com/rabotaem-incorporated/algebra-conspect-1course/master/sections/01-number-theory/08-primes.typ | typst | Other | #import "../../utils/core.typ": *
== Простые числа
#def[
Число $p in ZZ$ называется простым, если $p in.not {-1, 0, 1}$ и все делители $p$ --- это $plus.minus 1$ и $p$.
]
#prop[
+ $p$ --- простое $<==> -p$ --- простое.
+ $p$ --- простое, $a in ZZ ==> p divides a$ или $p bot a$.
+ $p, q$ --- простые $==> p sim q$ или $p bot q$.
+ $p divides a b ==> p divides a$ или $p divides b$.
]
#pr[
Пусть $a eq.not plus.minus 1$, тогда существует простое число $p : space p divides a$.
]
#proof[
Пусть $a = 0$, тогда $p = 239$
Тогда $a eq.not 0$, пускай $a > 0$, так как, случай $a < 0$ аналогичен.
Индукция по $a$:
"База": $a = 1$, но $a > 0$, значит простое число уже встречалось.
"Переход":
$a$ --- простое $==> p = a, space p divides a$
$a$ --- не простое, значит $exists d : space.quad 1 < d < a, space d divides a$
$a = d d'$, тогда по индукционному переходу существует простое число $p : space p divides d$
$p divides d, space d divides a ==> p divides a$
]
#def[
Составное число --- это число отличное от 0, и не являющееся простым.
]
#def[
Решето Эратосфена --- это алгоритм, который позволяет найти все простые числа от 1 до $n$.
$2, 3, 4, 5, 6, 7, 8, 9, ..., 100$
- 2 --- простое, вычеркиваем все числа кратные 2
- 3 --- простое, вычеркиваем все числа кратные 3
- 4 --- составное, пропускаем
- и. т. д.
В итоге получим все простые числа от $1$ до $100$.
]
#notice[
$PP$ --- множество всех простых чисел.
]
#th(name: "<NAME>")[
Существует бесконечно много простых чисел
]
#proof[
Пусть $p_1, p_2, ... p_n$ --- все простые числа. Возьмем $N = p_1 p_2 ... p_n + 1$, пусть оно составное $==>$
$exists p in PP : space p divides N, space p > 0 ==> exists j: space p = p_j$
Тогда, $p divides (N - 1) ==> p divides 1 ==> p = plus.minus 1$, противоречие.
] |
https://github.com/TheTacBanana/make_deedpoll | https://raw.githubusercontent.com/TheTacBanana/make_deedpoll/master/deed_poll.typ | typst | #import "@preview/nth:1.0.1": nth
#let CURRENT_DAY = datetime.today()
#let OLDNAME = [Old Name]
#let NEWNAME = [New Name]
#let CITY = [City]
#let COUNTY = [County]
#let POSTCODE = [Postcode]
#let ADDRESS = [Street Address]
#let WITNESS1 = [Witness One]
#let WITNESS1_ADDRESS = [Address]
#let WITNESS1_POSTCODE = [Postcode]
#let WITNESS2 = [Witness Two]
#let WITNESS2_ADDRESS = [Address]
#let WITNESS2_POSTCODE = [Postcode]
#align(center, text(20pt)[
*Deed of Change of Name*
])
#v(30pt)
#smallcaps[By this Deed of Change of Name] made by myself the undersigned #NEWNAME of #ADDRESS, #CITY,
#POSTCODE, in the county of #COUNTY, formerly known as #OLDNAME, a British Citizen under section 1(1) of the British
Nationality Act 1981.
#v(10pt)
*I hereby declare as follows:*
#v(10pt)
*I. #h(5pt) #smallcaps[I absolutely]* and entirely renounce, relinquish, and abandon the use of my said former name #OLDNAME and
assume, adopt, and determine to take and use from the date hereof the name of #NEWNAME in substitution for my former
name of #OLDNAME.
#v(20pt)
*II. #h(5pt) #smallcaps[I shall at all times]* hereafter in all records, deeds, documents, and other writings and in all
actions and proceedings, as well as in all dealings and transactions, and on all occasions whatsoever use and subscribe
the said name of #NEWNAME as my name, in substitution for my former name of #OLDNAME so relinquished as aforesaid to the
intent that I may hereafter be called, known, or distinguished not by the former name of #OLDNAME but by the name
#NEWNAME.
#v(20pt)
*III. #h(5pt) #smallcaps[I authorise and require]* all persons at all times to designate, describe, and address me by
the adopted name of #NEWNAME.
#v(20pt)
*#smallcaps[In witness]* whereof I have hereunto subscribed my adopted and substituted name of #NEWNAME and also my said
former name of #OLDNAME.
Notwithstanding the decision of Mr <NAME> in re Parrott, Cox v Parrott [1946] Ch 183, the applicant wishes the
enrolment to proceed.
*#smallcaps[Signed as a Deed this #nth(CURRENT_DAY.day()) day of #CURRENT_DAY.display("[month repr:long]") in the year #CURRENT_DAY.year()]*
#let SIGNATURE_LINE = {
box[
#underline(stroke: (dash: "dotted", thickness: 1pt))[
#for value in range(700) {
sym.space.hair
}
#h(0.000001pt)
]
]
}
#v(100pt)
#stack(dir: ltr, block(width: 50%)[
#align(center, [
#SIGNATURE_LINE \
By the above name\ #NEWNAME
#v(60pt)
#SIGNATURE_LINE \
#WITNESS1 \
#WITNESS1_ADDRESS, #WITNESS1_POSTCODE \
])
], block(width: 50%)[
#align(center, [
#SIGNATURE_LINE \
By the above name\ #OLDNAME
#v(60pt)
#SIGNATURE_LINE \
#WITNESS2 \
#WITNESS2_ADDRESS, #WITNESS2_POSTCODE \
])
]) |
|
https://github.com/Shedward/dnd-charbook | https://raw.githubusercontent.com/Shedward/dnd-charbook/main/main.typ | typst | #include "books/edna-zeenhoffer.typ"
|
|
https://github.com/0xPARC/0xparc-intro-book | https://raw.githubusercontent.com/0xPARC/0xparc-intro-book/main/src/mpc.typ | typst | #import "preamble.typ":*
= Garbled circuits
Imagine Alice and Bob each have some secret values
$a$ and $b$, and would like to jointly compute some function $f$ over
their respective inputs. Furthermore, they’d like to keep their secret
values hidden from each other: if Alice and Bob follow the protocol
honestly, they should both end up learning the correct value of
$f (a , b)$, but Alice shouldn’t learn anything about $b$ (other than
what could be learned by knowing both $a$ and $f (a , b)$), and likewise
for Bob.
Yao’s garbled circuits is one of the most well-known 2PC protocols.
The protocol is quite clever, and optimized variants of the protocol are
being
#cite("https://github.com/privacy-scaling-explorations/mpz/tree/dev/crates/mpz-garble")[implemented and used today];.
== The problem
<the-problem>
Here is our problem setting, slightly more formally:
- Alice knows a secret bitstring $a$ of length $m$ bits.
- Bob knows a secret bitstring $b$ of length $n$ bits.
- $f$ is a binary circuit, which takes in $m + n$ bits, and runs them
through some $k$ gates. The outputs of some of the gates are the
public outputs of the circuit. Without loss of generality, let’s also
suppose that each gate in $f$ accepts either $1$ or $2$ input bits,
and outputs a single output bit.
- Alice and Bob would like to jointly compute $f (a , b)$ without
revealing their secrets to each other.
== Outline of solution
Our solution will contain two key components:
- Alice constructs a _garbled circuit_
that takes in the value $b$ (whatever it is)
and spits out $f(a, b)$.
A _garbled circuit_, roughly speaking,
is an "encrypted" circuit that takes encrypted input and creates encrypted output.
- An _oblivious transfer_ is a protocol where Alice has two messages,
$m_0$ and $m_1$.
Bob can get exactly one of them, $m_i$,
without letting Alice know what $i$ is.
In this context, Alice ends up sending Bob a password
for his input in a way that
Bob doesn't learn the passwords for any other inputs,
and Alice doesn't find out which password she sent to Bob.
In slightly more detail:
1. Whatever the function $f$ is, we'll assume that it takes $m+n$ bits of input
$a_1, dots, a_m$ and $b_1, dots, b_n$,
and that it's computed by some sort of circuit
made of AND, OR and NOT gates.
2. Alice's first task is to "plug her own inputs into this circuit $f$."
The result will be a new circuit
(you might call it $f_a$)
that has just $n$ input slots
for Bob's $n$ bits $b_1, dots, b_n$.
3. Now, Alice is going to "garble" the circuit $f_a$.
Once it's garbled, Bob won't be able to see how it works.
He'll only be able to plug his own input $(b_1, dots, b_n)$
into the circuit.
4. To prevent Bob from plugging other inputs in as well,
a garbled circuit will require a "password"
for each input Bob wants to plug in --
a different password for every possible input.
If Bob has the password for $(b_1, dots, b_n)$,
he can learn $f_a (b_1, dots, b_n) = f(a, b)$,
but he won't learn anything else about how the circuit works.
5. Now, Alice has all the passwords for all the possible inputs, but how can she give Bob the password for $(b_1, dots, b_n)$?
Alice doesn't want to let Bob have any other passwords --
and Bob isn't willing to tell Alice which password he is asking for.
This is where we will use the "oblivious transfer."
We now flesh out this outline, starting with garbled circuits.
== Garbled gates
Our garbled circuits are going to be built out of _garbled gates_.
A garbled gate is like a traditional gate (like AND, OR, NAND, NOR),
except its functionality is hidden.
What does that mean? Let's say the gate has two input bits,
so there are four possible inputs to the gate:
$(0, 0), (0, 1), (1, 0), (1, 1)$.
For each of those four inputs $(x, y)$,
there is a secret password $P_(x, y)$.
The gate $G$ will only reveal its value $G(x, y)$
if you give it the password $P_(x, y)$.
Here is a natural approach to make a garbled gate.
Choose a _symmetric-key_#footnote[Symmetric-key encryption is probably
what you think of
when you think of plain-vanilla encryption:
You use a secret key $K$ to encrypt a message $m$,
and then you (or someone else) need the same secret key $K$ to decrypt it.]
encryption scheme
$Enc$ and publish the following table:
#table(
columns: 2,
inset: (x: 5pt, y: 8pt),
[$(0, 0)$], [$Enc_(P_(0, 0))(G(0, 0))$],
[$(0, 1)$], [$Enc_(P_(0, 1))(G(0, 1))$],
[$(1, 0)$], [$Enc_(P_(1, 0))(G(1, 0))$],
[$(1, 1)$], [$Enc_(P_(1, 1))(G(1, 1))$],
)
If you have the values $x$ and $y$,
and you know the password $P_(x, y)$,
you just go to the $(x, y)$ row of the table,
look up
$
Enc_(P_(x, y))(G(x, y)),
$
decrypt it, and learn $G(x, y)$.
But if you don't know the password $P_(x, y)$,
assuming $Enc$ is a suitably secure encryption scheme,
you won't learn anything about the value $G_(x, y)$
from its encryption.
== Chaining garbled gates
The next step to combine a bunch of garbled gates into a circuit.
We'll need to make two changes to the protocol.
1. To chain garbled gates together,
we need to modify the output of each gate:
In addition to outputting the bit $z = G_i (x, y)$,
the $i$-th gate $G_i$
will also output a password $P_z$ that Bob can use at the next step.
Now Bob has one bit coming in for the left-hand input $x$,
and it came with some password $P_x^(text("left"))$ --
and then another bit coming in for $y$,
with some password $P_y^(text("right"))$.
To get the combined password $P_(x, y)$,
Bob concatenates the two passwords $P_x^(text("left"))$ and $P_y^(text("right"))$.
2. To keep the functionality of the circuit hidden,
we don't want Bob to learn anything about the structure of
the individual gates --
even the single bit he gets as output.
This is an easy fix:
Instead of having the gate output
both the bit $z$ and the password $P_z$,
we'll have the gate just output $P_z$.
But now how does Bob know what values to feed into the next gate?
The left-hand column of the "gate table"
needs to be indexed by the passwords
$P_x^(text("left"))$ and $P_y^(text("right"))$,
not by the bits $(x, y)$.
But we don't want Bob to learn the other passwords from the table!
Let's say this again. We want:
- If Bob knows both passwords $P_x^(text("left"))$ and $P_y^(text("right"))$,
Bob can find the row of the table for the input $(x, y)$.
- If Bob doesn't know the passwords, he can't learn them by looking at the table.
Of course, the solution is to use a hash function!
So here is the new version of our garbled gate.
For simplicity, we'll assume it's an AND gate --
so the outputs will be (the passwords encoding) 0, 0, 0, 1.
#table(
columns: 2,
inset: (x: 5pt, y: 8pt),
[$hash(P_0^(text("left")), P_0^(text("right")))$], [$Enc_(P_0^(text("left")), P_0^(text("right"))) (P_0^(text("out")))$],
[$hash(P_0^(text("left")), P_1^(text("right")))$], [$Enc_(P_0^(text("left")), P_1^(text("right"))) (P_0^(text("out")))$],
[$hash(P_1^(text("left")), P_0^(text("right")))$], [$Enc_(P_1^(text("left")), P_0^(text("right"))) (P_0^(text("out")))$],
[$hash(P_1^(text("left")), P_1^(text("right")))$], [$Enc_(P_1^(text("left")), P_1^(text("right"))) (P_1^(text("out")))$],
)
== How Bob uses one gate
Let's play through one round of Bob's gate-using protocol.
1. Suppose Bob's input bits are 0 (on the left) and 1 (on the right).
Bob doesn't know he has 0 and 1 (but we do!).
Bob knows his left password is some value
$P_0^(text("left"))$,
and his right password is some other value
$P_1^(text("right"))$.
2. Bob takes the two passwords, concatenates them, and computes a hash.
Now Bob has
$
hash(P_0^(text("left")), P_1^(text("right"))).
$
3. Bob finds the row of the table indexed by
$hash(P_0^(text("left")), P_1^(text("right")))$,
and he uses it to look up
$
Enc_(P_0^(text("left")), P_1^(text("right"))) (P_0^(text("out"))).
$
4. Bob uses the concatenation of the two passwords
$P_0^(text("left")), P_1^(text("right"))$
to decrypt
$P_0^(text("out")).$
5. Now Bob has the password for the bit 0 to feed into the next gate --
but he doesn't know his bit is 0.
So Bob is exactly where he started:
he knows the password for his bit, but he doesn't know his bit.
So we can chain together as many of these garbled gates as we like
to make a full garbled circuit.
== How the circuit ends
At the end of the computation,
Bob needs to learn the final result.
How?
Easy!
The final output gates are different from the intermediate gates.
Instead of outputting a password,
they will just output the resulting bit in plain text.
== How the circuit starts
This is trickier.
At the beginning of the computation,
Bob needs to learn the passwords for all of his input bits. Let's just frame the problem for a single bit.
- Alice has two passwords, $P_0$ and $P_1$.
- Bob has a bit $b$, either $0$ or $1$.
- Bob wants to learn one of the passwords, $P_b$, from Alice.
- Bob does not want Alice to learn the value of $b$.
- Alice does not want Bob to learn the other password.
This is where _oblivious transfer_ comes in, which we'll see in @ot.
|
|
https://github.com/tingerrr/anti-matter | https://raw.githubusercontent.com/tingerrr/anti-matter/main/src/core.typ | typst | MIT License | /// Get state which keeps track of numbering patterns.
///
/// - label (label): the label which is used for document fences
/// - numbering (array): the default numberings to start with
/// -> counter
#let numbering-state(
label: <anti-matter:fence>,
numbering: ("I", "1", "I"),
) = state("anti-matter:state", (
label: label,
numbering: numbering,
))
/// Get the counter which keeps track of the inner page number.
///
/// -> counter
#let inner-counter() = counter("anti-matter:inner-counter")
/// Get the counter which keeps track of the outer page number.
///
/// -> counter
#let outer-counter() = counter("anti-matter:outer-counter")
/// Retreive the part at the given location.
///
/// - loc (location): the location at which to get the part for
/// -> str
#let part(loc) = {
let label = numbering-state().at(loc).label
let fences = query(label, loc)
let fence-1 = fences.first().location()
let fence-2 = fences.last().location()
if loc.page() <= fence-1.page() {
"front"
} else if fence-1.page() < loc.page() and loc.page() <= fence-2.page() {
"inner"
} else {
"back"
}
}
/// Select the counter and numbering index for the given part.
///
/// - part (str): the part for which to get the numbering for (must be one of `front`, `inner`,
/// `back`)
/// -> (array, none)
#let select(part) = (
front: (outer-counter(), 0),
inner: (inner-counter(), 1),
back: (outer-counter(), 2),
).at(part, default: none)
|
https://github.com/TypstApp-team/typst | https://raw.githubusercontent.com/TypstApp-team/typst/master/docs/guides/welcome.md | markdown | Apache License 2.0 | ---
description: Guides for Typst.
---
# Guides
Welcome to the Guides section! Here, you'll find helpful material for specific
user groups or use cases. Currently, two guides are available: An introduction
to Typst for LaTeX users, and a detailed look at page setup. Feel free to
propose other topics for guides!
## List of Guides
- [Guide for LaTeX users]($guides/guide-for-latex-users)
- [Page setup guide]($guides/page-setup-guide)
|
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.