vault backup: 2026-04-16 17:07:54

This commit is contained in:
2026-04-16 17:07:54 -04:00
parent 901925883d
commit 7036c0f542
16 changed files with 266 additions and 44 deletions
+6
View File
@@ -17,6 +17,7 @@
"showStatusBar": true,
"updateSubmodules": false,
"syncMethod": "merge",
"mergeStrategy": "none",
"customMessageOnAutoBackup": false,
"autoBackupAfterFileChange": false,
"treeStructure": false,
@@ -34,6 +35,11 @@
"authorInHistoryView": "hide",
"dateInHistoryView": false,
"diffStyle": "split",
"hunks": {
"showSigns": false,
"hunkCommands": false,
"statusBar": "disabled"
},
"lineAuthor": {
"show": true,
"followMovement": "same-commit",
+1 -1
View File
@@ -11,7 +11,7 @@ type: article
title: Rev. William Alexander And Wife Killed In Airplane Crash
url: https://gateway.okhistory.org/ark:/67531/metadc2193346/
authors:
- Peterson, Robert H.
- Robert H. Peterson
journal: Durant Daily Democrat (Durant, Okla.)
volume: 59
number: 172
+2 -1
View File
@@ -8,7 +8,8 @@ tags:
- exclude-from-word-count
- topic/software
- type/media/book
author: Alan Mark Davis
authors:
- Alan Mark Davis
date: 1990
dg-publish: false
---
+2 -1
View File
@@ -9,7 +9,8 @@ tags:
- status/complete
- topic/hobbies/poetry
- type/media/poetry
author: Karel Čapek
authors:
- Karel Čapek
booktitle: "Intimate Things: Stories from Everyday Life"
language: English
origlanguage: Czech
+1 -1
View File
@@ -61,7 +61,7 @@ dg-publish: true
(0.2,2.5)
} -- cycle;
% (Optional) label hull vertices
% label hull vertices
\addplot[only marks, mark=*, mark size=2.2pt] coordinates {
(0.5,0.5)
(3.0,0.5)
+8 -2
View File
@@ -2,8 +2,14 @@
id:
aliases: []
title: How to Measure Anything in Project Management
tags: []
author: Douglas W. Hubbard & Dr. Alexander Budzier & Andreas Bang Leed
tags:
- authorship/other
- destiny/permanent
- type/media/book
authors:
- Douglas W. Hubbard
- Dr. Alexander Budzier
- Andreas Bang Leed
---
# How to Measure Anything in Project Management
+11 -17
View File
@@ -308,9 +308,7 @@ In other than dwelling units, in addition to the requirements in 110.16(A), a pe
> ANSI Z535.4-2011, Product Safety Signs and Labels, provides guidelines for the design of safety signs and labels for application to products.
> [!info] Informational Note No. 3:
> Acceptable industry practices for equipment labeling are described in NFPA 70E-2018, Standard for Electrical
Safety in the Workplace. This standard provides specific criteria for developing arc-flash labels for equipment that provides nominal system voltage, incident energy levels, arc-flash boundaries, minimum required levels of personal protective equipment, and so forth.
> Acceptable industry practices for equipment labeling are described in NFPA 70E-2018, Standard for Electrical Safety in the Workplace. This standard provides specific criteria for developing arc-flash labels for equipment that provides nominal system voltage, incident energy levels, arc-flash boundaries, minimum required levels of personal protective equipment, and so forth.
### 110.18 Arcing Parts.
@@ -356,7 +354,8 @@ Reconditioned equipment shall be identified as "reconditioned" and the original
Where caution, warning, or danger signs or labels are required by this Code, the labels shall meet the following requirements:
* (1) The marking shall warn of the hazards using effective words, colors, symbols, or any combination thereof.
* (1) The marking shall warn of the hazards
using effective words, colors, symbols, or any combination thereof.
> [!info] Informational Note:
> ANSI Z535.4-2011, Product Safety Signs and Labels, provides guidelines for suitable font sizes, words, colors, symbols, and location requirements for labels.
@@ -799,9 +798,9 @@ Doors shall be equipped with locks, and doors shall be kept locked, with access
Where a transformer is installed in a vault as required by Article 450, the vault shall be constructed in accordance with the requirements of Part III of Article 450.
> [!info] Informational Note No. 1:
> For additional information, see ANSI/ASTM E119-2018a, Method for Fire Tests of Building Construction and
Materials, and NFPA 80-2019, Standard for Fire Doors and Other Opening Protectives.
> For additional information, see ANSI/ASTM E119-2018a,
> Method for Fire Tests of Building Construction and Materials,
> and NFPA 80-2019, Standard for Fire Doors and Other Opening Protectives.
> [!info] Informational Note No. 2:
> A typical 3-hour construction is 150 mm (6 in.) thick reinforced concrete.
@@ -945,17 +944,12 @@ The points of control shall be located so that persons are not likely to come in
Unguarded live parts above working space shall be maintained at elevations not less than required by Table 110.34(E).
Table 110.34(E) Elevation of Unguarded Live Parts
Table 110.34(E) Elevation of Unguarded Live Parts Above Working Space
Above Working Space
Nominal Voltage
Between Phases
Elevation m ft
1001--7500 V 2.7 9
7501--35,000 V 2.9 9 ft 6 in.
| Nominal Voltage Between Phases | Elevation |
| ------------------------------ | ----------------- |
| 1001--7500 V | 2.7m (9 ft) |
| 7501--35,000 V | 2.9m (9 ft 6 in.) |
Over 35 kV Add 9.5 mm per kV above 35 kV
+13 -15
View File
@@ -714,7 +714,7 @@ Intermediate supports shall be provided
as necessary to limit supported conductor lengths
to not greater than those values specified in Table 300.19(A).
#### Table 300.19(A) Spacings for Conductor Supports ^t300-19a
#### Table 300.19(A) Spacings for Conductor Supports
| Conductor Size | Aluminum or Copper-Clad Aluminum | Copper |
| -------------------------------- | --------------------------------:| ------:|
@@ -731,33 +731,31 @@ to not greater than those values specified in Table 300.19(A).
Support methods and spacing intervals for fire-rated cables and conductors
shall comply with any restrictions provided in the listing
of the electrical circuit protective system used
and in no case shall exceed the values in [[#^t300-19a|Table 300.19(A)]].
and in no case shall exceed the values in [[#Table 300.19(A) Spacings for Conductor Supports|Table 300.19(A)]].
#### 300.19(C) Support Methods.
One of the following methods of support shall be used:
1. Clamping devices constructed of or employing insulating wedges
inserted in the ends of the raceways.
Where clamping of insulation does not adequately support the cable,
the conductor also shall be clamped.
inserted in the ends of the raceways.
Where clamping of insulation does not adequately support the cable,
the conductor also shall be clamped.
2. Inserting boxes at the required intervals
in which insulating supports are installed and secured
in an approved manner to withstand the weight of the conductors attached thereto,
the boxes being provided with covers.
in which insulating supports are installed and secured
in an approved manner to withstand the weight of the conductors attached thereto,
the boxes being provided with covers.
3. In junction boxes, deflecting the cables not less than 90 degrees
and carrying them horizontally to a distance not less than twice the diameter of the cable,
the cables being carried on two or more insulating supports
and additionally secured thereto by tie wires, if desired.
Where this method is used, cables shall be supported at intervals
not greater than 20 percent of the support spacing in [[#^t300-19a|Table 300.19(A)]].
and carrying them horizontally to a distance not less than twice the diameter of the cable,
the cables being carried on two or more insulating supports
and additionally secured thereto by tie wires, if desired.
Where this method is used, cables shall be supported at intervals
not greater than 20 percent of the support spacing in [[#Table 300.19(A) Spacings for Conductor Supports|Table 300.19(A)]].
4. Other approved means.
%% TODO: TEXT OMITTED %%
### 300.20 Induced Currents in Ferrous Metal Enclosures or Ferrous Metal Raceways.
#### 300.20(A) Conductors Grouped Together.
+2 -1
View File
@@ -7,7 +7,8 @@ tags:
- topic/construction/electrical
- topic/estimating
- type/media/article
author: Godwin Ashley Dilibe Offiah
authors:
- Godwin Ashley Dilibe Offiah
date: 2017
---
# Qualitative Analysis of Lost Labor Productivity in Electrical Construction from the Perspective of Field Personnel
+2 -1
View File
@@ -5,7 +5,8 @@ title: And to Think That I Saw It on Mulberry Street
tags:
- exclude-from-word-count
- type/media/poetry
author: Dr. Seuss
authors:
- Dr. Seuss
date: 1937
---
# And to Think That I Saw It on Mulberry Street
+2 -1
View File
@@ -8,7 +8,8 @@ tags:
- status/incomplete
- topic/construction/electrical
- type/media/article
author: David A. Snyder, PE
authors:
- David A. Snyder, PE
dg-publish: false
year: 2020
---
+2 -1
View File
@@ -10,7 +10,8 @@ tags:
- topic/math/statistics
- topic/risk
- type/media/book
author: Nassim Nicholas Taleb
authors:
- Nassim Nicholas Taleb
identifiers:
- isbn:0-8129-7521-9
- oclc:60349198
+1 -1
View File
@@ -8,7 +8,7 @@ tags:
- exclude-from-word-count
- status/complete
- type/media/poetry
author:
authors:
- Alfred Lord Tennyson
dg-publish: true
---
+1 -1
View File
@@ -76,7 +76,7 @@ you are vastly underestimating the number of ideas you have.
At scale you won't be able to distinguish between
"Concise explanations accelerate progress"
and "Accelerating progress explanations",
and if titles-as-filenames doesn't aid organization
and if titles-as-filenames don't aid organization
you might as well use timestamps, which do.
***
+171
View File
@@ -0,0 +1,171 @@
---
id: 2026-04-16T12:55:49-04:00
aliases: []
title: 2026-04-16 12:55:49
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/timestamped
dg-publish: true
date-created: 2026-04-16T12:55:49-04:00
daily: "[[2026-04-16]]"
weekly: "[[2026-W16]]"
monthly: "[[2026-04]]"
quarterly: "[[2026-Q2]]"
yearly: "[[2026]]"
---
# 2026-04-16 12:55:49
## Batch Creating Bluebeam Revu Length Measure Annotations
I've been trying for years now
to figure out how to batch create PDF markups
understood by the Bluebeam Revu as length measurements.
The most practical route I've found so far
is to batch create polyline annotations through a PDF editing library,
export these markups to Revu's XML based .bax format,
edit the XML, then reimport the modified .bax file.
### Converting a Polyline to a Bluebeam Polylength
#### Export Markups
Below is a .bax file for a single-page letter-sized PDF document
with only two markups,
one standard polyline,
and one polylength measurement.
```
<?xml version="1.0" encoding="utf-8"?>
<Document Version="1">
<Page Index="0">
<Label>1</Label>
<Width>612</Width>
<Height>792</Height>
<Annotation>
<Page>1</Page>
<Contents />
<ModDate>2026-04-16T10:34:28.0000000Z</ModDate>
<Color>#FF0000</Color>
<Type>PolyLine</Type>
<ID>QYMFSTEOUXIEHCPW</ID>
<TypeInternal>Bluebeam.PDF.Annotations.AnnotationPolyline</TypeInternal>
<Raw>789c<!--HEX TRUNCATED--></Raw>
<Index>0</Index>
<Subject>PolyLine</Subject>
<CreationDate>2026-04-16T10:34:28.0000000Z</CreationDate>
<Author>zmeyers</Author>
</Annotation>
<Annotation>
<Page>1</Page>
<Contents>15'-7"</Contents>
<ModDate>2026-04-16T10:35:00.0000000Z</ModDate>
<Color>#FF0000</Color>
<Type>PolyLine</Type>
<ID>BMHFFZSZURMLPTRN</ID>
<TypeInternal>Bluebeam.PDF.Annotations.AnnotationMeasurePolylength</TypeInternal>
<Raw>789cad92d<!--HEX TRUNCATED--></Raw>
<Index>1</Index>
<Subject>Polylength Measurement</Subject>
<CreationDate>2026-04-16T10:34:50.0000000Z</CreationDate>
<Author>zmeyers</Author>
</Annotation>
<Scale>
<Page>1</Page>
<ID>RKEGIABVKDXPBWJP</ID>
<Raw>789c<!--HEX TRUNCATED--></Raw>
<Ratio>0.25 in = 1 ft' in"</Ratio>
<Index>-1</Index>
<X1>0</X1>
<Y1>0</Y1>
<X2>612</X2>
<Y2>792</Y2>
</Scale>
</Page>
<GlobalResources>
<Resource>
<ID>789cf37<!--HEX TRUNCATED--></Raw>
</Resource>
<Resource>
<ID>789c<!--HEX TRUNCATED--></ID>
<Raw>789c<!--HEX TRUNCATED--></Raw>
</Resource>
</GlobalResources>
</Document>
```
#### Change `<TypeInternal>`
Change the `<TypeInternal>` property of the polyline
from `Bluebeam.PDF.Annotations.AnnotationPolyline`
to `Bluebeam.PDF.Annotations.AnnotationMeasurePolylength`
#### Change `<Raw>`
##### Decode and Decompress
Decode and decompress the value of the `<Raw>` property.
> [!info]
> The standard header `789c`
> indicates the data is zlib-compressed binary,
> encoded as hexadecimal.
```python
# decompress_hex.py
import zlib
import binascii
import sys
raw_hex = sys.argv[1]
data = binascii.unhexlify(raw_hex)
decompressed = zlib.decompress(data)
print(decompressed)
```
The resultant text is a PDF object
resembling the following:
```pdf
<</Vertices[161.8211 574.2108 279.8409 669.1133 407.5944 594.2863]/IC[1 0 0]/T(zmey...>>
```
##### Modify the Object
Insert the following key-value pair:
```
/Measure/BBObjPtr_XXXXXXXXXXXXXXXX
```
where `XXX...` is the name of the Scale object.
It may be most straightforward to copy this key-value pair
from a manually created length measurement on the same page.
##### Recompress and Reencode
```python
# compress_to_hex.py
import zlib
import binascii
import sys
text = sys.argv[1]
compressed = zlib.compress(text.encode('utf-8'))
hex_encoded = binascii.hexlify(compressed).decode('ascii')
print(hex_encoded)
```
Replace the old value of `<Raw>` with the modified hex.
#### Reimport Markups
In the target PDF,
open the markup summary,
delete all markups,
then reimport.
+41
View File
@@ -0,0 +1,41 @@
---
id: 2026-04-16T14:26:45-04:00
aliases: []
title: 2026-04-16 14:26:45
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/timestamped
dg-publish: true
date-created: 2026-04-16T14:26:45-04:00
daily: "[[2026-04-16]]"
weekly: "[[2026-W16]]"
monthly: "[[2026-04]]"
quarterly: "[[2026-Q2]]"
yearly: "[[2026]]"
---
# 2026-04-16 14:26:45
## Distance Between Two Points
```excel
=LET(minorDif,MIN([@[top-dif]],[@[left-dif]]),
majorDif,MAX([@[top-dif]],[@[left-dif]]),
SQRT(2*minorDif^2)+(majorDif-minorDif)
)
```
```python
import math
x_dif = math.abs(x2 - x1)
y_dif = math.abs(y2 - y1)
ortholinear_distance = x_dif + y_dif
minor_dif = min(y_dif, x_dif)
major_dif = max(y_dif, x_dif)
octolinear_distance = math.sqrt(2 * minor_dif^2) + (majorDif - minorDif)
```