Rawer

Under Construction

there are many to-dos

#

Two Steps Back

I've spent the past few hours at desk going around in circle with module loading in #:transmissions. Most of this was down to my over-reliance on Claude AI. The code required for core operations is just a bit too complex.

But one reason for this will be my use of repopack as-is for project knowledge. I need RAG material to be custom to the target. My own repopack.

Need docs.

A renaming refactoring first : execute() -> process(). Everywhere!

Ok, for now I'll use :

transmissions/src/processors/staging/

for new stuff. Get back to module loading when I've got my own repopack.

Break time.

also later:

  • make the claude-json-to-md thing in staging

Renaming

Hmm. Looks like I've changed things since I last used the Jasmine tests. But I've still got p (#:postcraft runner) and ./trans test_fork (a fairly simple runner) as integration tests.

grep -r "process" | grep ".js"

grep -r ".js" | grep -v "^processors" | grep "process"

grep -r "execute" | grep -v "^node_modules" | grep ".md"

cd src
grep -r execute | grep ".js" | grep -v "^processors"
...
engine/Transmission.js:  async execute(message) {
engine/Transmission.js:      logger.error("No valid processor found to execute")
engine/Transmission.js:  async execute(message) {
engine/Transmission.js:    //  processor.execute(message)
engine/TransmissionRunner.js:                    await transmission.execute(message)
simples/nop/nop copy.js:message = await p10.execute(message)
simples/nop/nop copy.js:// message = await p20.execute(message)
simples/nop/nop.js:message = await nop.execute(message)
simples/nop/simple-runner.js:    const outputs = await processor.execute(message)
simples/nop/simple-runner.js:    var outputs = await nop.execute(message)
simples/nop/simple-runner.js:    outputs = await fork.execute(message)
simples/env-loader/env-loader.js:message = await p10.execute(message)
simples/env-loader/env-loader.js:message = await p20.execute(message)

grep -r ".execute" | grep ".js" | grep -v "^processors"

cd ../tests
grep -r "execute" | grep ".js"

Please give me a command that will scan the current directory tree and replace all occurrences in files of the string " execute(" with " process("

Please give me a command that will scan the current directory tree and replace all occurrences in files of the string ".execute(" with ".process("

cd src
find . -type f -exec sed -i 's/ execute(/ process(/g' {} +
find . -type f -exec sed -i 's/\.execute(/\.process(/g' {} +

cd ../tests
find . -type f -exec sed -i 's/ execute(/ process(/g' {} +
find . -type f -exec sed -i 's/\.execute(/\.process(/g' {} +

and in
../docs/postcraft

Ok. Seems good. Time I committed.

Two Steps Back

2024-10-26
#

Rare

my phone is displaying the r4 prog 'Rare Earth'

  • run all postcrafts
  • VocBench transmission
  • Transmissions refactoring

fix:

./trans ../trans-apps/applications/module-load-test  -m {"first":"one","second":"two"}

Need to refactor CommandUtils.js - run.js helpers

verify:

 ./trans ../trans-apps/applications/claude-json-converter ../trans-apps/applications/claude-json-converter/conversations.json

Rare

2024-10-26
#

Coherence

  • Claude dump app
  • ClaudioB

#:todo check Claude Computer #:todo check #:hyperdata-desktop - can I add a hook to control the UI?

Claude dump app

#:todo make a repopack-style transmission

transmissions/prompts/claude-to-sparql-app.md

#:todo repl

Coherence

2024-10-26
#

Damp

It's wet out again also my spirits are a little soggy.

  • publish #:postcrafts now! It's quite an interesting little task but it's close enough to admin to feel like a chore and I keep getting distracted...

Quick look at VocBench (below)...moving on...where was I...

cd ~/github-danny/transmissions
./trans ../server/deploy

Ok, transmissions/src/applications/postcraft/transmission.ttl includes :

:s10 a :DatasetReader . # read the manifest
# trm:configKey trm:describe .

:s20 a :ConfigMap ;
    trm:configKey :postcraftMap .

Hang on, how am I doing the multi-pipeline call (#:todo rename pipeline -> transmission) for #:postcraft..?

#:todo automate creation of project handover #:ho docs for my future self

Ok, ./trans calls run.js which calls transmissions/src/utils/CommandUtils.js.

The CommandUtils.run() calls transmissions/src/engine/TransmissionBuilder.js to build all the transmissions in transmissions.ttl and then runs them.

TransmissionBuilder.js has :

for (const q of poi.out(ns.rdf.type).quads()) {
  if (q.object.equals(ns.trm.Pipeline)) {

Didn't I do something for running transmissions from transmissions (like a gosub)..?

wtf is :

class ProcessProcessor extends Processor {

!?

Ffs, I'd also forgotten about transmissions/src/engine/WorkerPool.js. That would be handy for spawing subs. Jeez. I have no idea, maybe I dreamt it. Ok, time for a repopack, ask Claude if he remembers.

VocBench

Ah, I do have to go on a slight tangent first. Little bit of vocab needed. Coincidentally Claudio B. reminded me about VocBench the other day, just what I need. I'm pretty sure I've used it before, can't remember at all. Can't see it on this machine, downloaded, unzipped, giving me a fun path. Semantic Turkey! - love it.

danny@danny-desktop:~/Apps/VocBench/vocbench3-12.2.0-full/semanticturkey-12.2/bin$ ./semanticturkey.sh

   ____                    __  _       ______         __
  / __/__ __ _  ___ ____  / /_(_)___  /_  __/_ ______/ /_____ __ __
 _\ \/ -_)  ' \/ _ `/ _ \/ __/ / __/   / / / // / __/  '_/ -_) // /
/___/\__/_/_/_/\_,_/_//_/\__/_/\__/   /_/  \_,_/_/ /_/\_\__/\_,  /
                                                            /___/

Developed by ART (Artificial Intelligence Research at Tor Vergata).
Version: 12.2. Build: 2024-07-09T11:01:05Z. Spring Boot version: 3.2.5


ST Started

Good-o, running nicely, access via http://localhost:1979/vocbench3

Ah. Claudio mentioned the manual. Now I see why. This thing seems big and arcane.

I'll leave for now, hack the Turtle for the terms I need, get back to that manual later.

Damp

2024-10-26
#

Hat

because my hat is on the desk

I'm in the process of setting up #:server infrastructure so all the #:postcraft instances (ie. rendering for my docs) can be run from a single command (using #:transmissions).

I've already got per-instance manifest.ttl files describing where things should go. I need an uber-manifest to run all of these. I'll need a few more vocab terms (and really need to refactor those). Coincidentally, the other day I stumbled on a vocab I did in 2001 :

RDF Process Profile (RPP) Specification 0.0.1

archive.org

Claude summarises :

RDF Process Profile (RPP) is a lightweight XML-based specification from 2001 that describes processes using RDF (Resource Description Framework). It aims to standardize how data processors are described, moving away from data-centric approaches toward resource-centric ones. RPP allows both online and offline processes to be represented as web resources, with descriptions of all required resources needed to carry out data processing. The specification includes a vocabulary of classes (like Profile, Component, Algorithm) and properties (like location, availability, input/output) that can be used to describe processes. RPP is designed to be extensible and can serve as a foundation for more sophisticated layers of process description, potentially enabling automated process discovery and execution.

rapper -i rdfxml -o turtle rpp.rdfs > rpp.ttl

#:todo note dead legacy domains : http://www.isacat.net /citnames/2001/04/rpp.htm https://web.archive.org/web/20021009222134/http://www.isacat.net/

Ok, I've set up :

@prefix rpp: <http://purl.org/stuff/rpp/> .

Hat

2024-10-26