refactors

kamangir · Jan 4, 2025 · dbeb61a · dbeb61a
1 parent c5a9bac
commit dbeb61a
Show file tree

Hide file tree

Showing 6 changed files with 20 additions and 5 deletions.
diff --git a/giza.bib b/giza.bib
@@ -1,3 +1,16 @@
+@Misc{aliases,
+  title =        "{Aliases (Bash Reference Manual)}",
+  howpublished = "\url{https://www.gnu.org/software/bash/manual/html_node/Aliases.html}",
+}
+
+
+@misc{NetworkX,
+  author =       "NetworkX Developers",
+  title =        "{NetworkX}",
+  year =         "2023",
+  howpublished = "\url{https://networkx.org/}",
+}
+
 @Misc{textualize_founded,
   author =       "Will McGugan",
   title =        "{Why I Founded Textualize}",

diff --git a/gizai/__init__.py b/gizai/__init__.py
@@ -4,7 +4,7 @@
 
 DESCRIPTION = f"{ICON} A Mathematical model for AI languages."
 
-VERSION = "7.136.1"
+VERSION = "7.138.1"
 
 REPO_NAME = "giza"
 

diff --git a/tex/access.tex b/tex/access.tex
@@ -24,4 +24,6 @@ \section{Access}
 
 \input{access/conventions/help}
 
-\input{access/conventions/init}
+\input{access/conventions/init}
+
+\input{access/conventions/namespaces}
diff --git a/tex/access/conventions/namespaces.tex b/tex/access/conventions/namespaces.tex
@@ -0,0 +1,2 @@
+\marginpar{\keyword{namespaces}}
+The Bash function \keyword{<func>} that has received the task \keyword{<task>} could redirect to the function \keyword{<func>_<task>}. We use this \emph{namespacing}~\cite{namespaces} mechanism for organization as well as orchestration. In practice, this leads to callables with multiple prefixes. We generate `@<keyword>` aliases~\cite{aliases} to facilitate user access. 
diff --git a/tex/automation.tex b/tex/automation.tex
@@ -6,6 +6,4 @@ \section{Automation}
 
 \input{automation/options}
 
-% TODO: aliases
-
 \input{automation/seed}
diff --git a/tex/automation/workflows.tex b/tex/automation/workflows.tex
@@ -1,2 +1,2 @@
 \marginpar{\keyword{workflows}}
-A \keyword{workflow} is a set of commands that depend on each other because they consume objects that are generated by other commands, among other reasons. We model a workflow as a Directed Acyclic Graph (DAG), where each node is a command. We use this abstraction to run workflows on AWS Batch~\cite{aws_batch} and Argo Workflows~\cite{argoflow}.
+A \keyword{workflow} is a set of commands that depend on each other because they consume objects that are generated by other commands, among other reasons. We model a workflow as a Directed Acyclic Graph (DAG), where each node is a command. We use this abstraction through \keyword{NetworkX}~\cite{NetworkX} to run workflows on AWS Batch~\cite{aws_batch} and Argo Workflows~\cite{argoflow}.
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1,2 @@
		\marginpar{\keyword{namespaces}}
		The Bash function \keyword{<func>} that has received the task \keyword{<task>} could redirect to the function \keyword{<func>_<task>}. We use this \emph{namespacing}~\cite{namespaces} mechanism for organization as well as orchestration. In practice, this leads to callables with multiple prefixes. We generate `@<keyword>` aliases~\cite{aliases} to facilitate user access.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -6,6 +6,4 @@ \section{Automation}

		\input{automation/options}

		% TODO: aliases

		\input{automation/seed}