vault backup: 2026-03-16 08:29:28

This commit is contained in:
2026-03-16 08:29:29 -04:00
parent 91bbe285c5
commit cfd3cc182f
2 changed files with 42 additions and 1 deletions
+1 -1
View File
@@ -24,7 +24,7 @@ dg-publish: false
## Chapter 2 Wiring and Protection
* [[nfpa-70_200|200 Use and Identification of Grounded Conductors]]
* [[nfpa-70_200_grounded-conductors|200 Use and Identification of Grounded Conductors]]
* [[nfpa-70_210_branch-circuits|210 Branch Circuits]]
* [[nfpa-70_215_feeders|215 Feeders]]
* [[nfpa-70_220_load-calculations|220 Branch-Circuit, Feeder, and Service Load Calculations]]
+41
View File
@@ -0,0 +1,41 @@
---
id: 2026-03-13T09:47:42-04:00
aliases: []
title: 2026-03-13 09:47:42
tags:
- authorship/original
- destiny/permanent
- status/draft
- type/periodic/timestamped
daily: "[[2026-03-13]]"
date-created: 2026-03-13T09:47:42-04:00
dg-publish: true
monthly: "[[2026-03]]"
quarterly: "[[2026-Q1]]"
weekly: "[[2026-W11]]"
yearly: "[[2026]]"
---
# 2026-03-13 09:47:42
I frequently have ideas of automation for [[construction-estimating]],
but I am often discouraged to the point of abandoning them
when considering the possibility that their use may not be permitted
because they can not be implemented with existing processes and tools.
For example, measuring unit subfeeds manually in LiveCount
is a monotonous and labor intensive activity
that could, as a single task, be automated very simply
with a search algorithm like [A*](https://en.wikipedia.org/wiki/A*_search_algorithm).
Such a program could also calculate voltage drop.
I think, though, I may have been unfair to my employers (current and previous).
Innovative methods will always be bottlenecked by Accubid's strict input pattern,
but there are still opportunities for improvement
that can comply with existing expectations of evidence.
For the unit subfeeds example,
a program could be made to draw the paths
with colors by cable type
and a legend with counts and total lengths,
writing the markup to PDF or TIFF
which could be uploaded