This version is out of date, covering development from v9.0.0 to v9.3.0. It is maintained here only for inbound reference links from elsewhere. It is no longer actively updated.

Jump to the current version of aTbRef

Tinderbox v9 Icon

Tagger performance and update time

This a new feature and Tinderbox is, at present, very conservative about the frequency at which Taggers run. It may be too conservative. A concern is that not all Macs have dedicated neural engine cores, and setting up a tagging scan requires a certain amount of prep work. The general idea here is that you want rules and agents to run now, but taggers are a sort of background discovery task.

The original notion for taggers is that they are slowly mining data and marking down relevant things they discover. They are envisioned like good research assistants; they may not get things done right away, but eventually they will get answers that are interesting and usually useful.

As taggers all run on document open, saving and re-opening the document is a reliable way to force the process to update on demand, at least until this feature evolves further control methods. Editing a note's text will also update the tagger. But, it will not update the displayed note, so to see the effect in the Displayed Attributes table it will be necessary to re-select the note.

Another way to force everything to be retagged is to edit the text of the tagger. However, tagging tasks and indexing tasks might be delayed in large documents when lots of things are going on, e.g. complex actions in rule or edicts using a lot of regex tasks, or very complex find() queries.

From v9.1.0, editing a tagger note marks the tagger as needing to be reloaded when the index is next revised.