|
|
|
|
|
|
|
|
|
|
|
|
|
|
# Changelog / Journal |
|
|
# Changelog / Journal |
|
|
|
|
|
|
|
|
|
|
|
## 20200623_M [Server 3.2.2, Engine 3.2.2] |
|
|
|
|
|
- Removed saccades algorithm to provide more comprehensive scanning. This will allow SNF to |
|
|
|
|
|
operate as a feature extractor for machine learning algorithms by matching "above-band" rules |
|
|
|
|
|
that do not compete with normal "in-band" rules. |
|
|
|
|
|
|
|
|
|
|
|
The growing use of above-band rule groups like "Experimental Bulk/Noisy" and additional groups |
|
|
|
|
|
for machine learning feature extraction has changed the paradigm for heuristic competition in |
|
|
|
|
|
the SNF world. Where previously it was important to optimize scanning performance for low-powered |
|
|
|
|
|
hardware and heuristic competition could add pressure to select for more efficient rules; the |
|
|
|
|
|
new paradigm requires that any available patterns will match (at least once) and hardware |
|
|
|
|
|
constraints are no longer a serious concernt. For example, SNF is easily able to operate at |
|
|
|
|
|
scanning rates that are 3 orders of magnitude higher than most deployments require on modern |
|
|
|
|
|
equipment. |
|
|
|
|
|
|
|
|
|
|
|
This isn't to say that heuristic efficiency optimization will be going away -- but rather that |
|
|
|
|
|
the mechanisms for optimizing that efficiecncy can be moved more toward the back-end so that |
|
|
|
|
|
the front-end scanners can concentrate on making all available matches available for analysis |
|
|
|
|
|
and even more sophisticated learning algorithms. |
|
|
|
|
|
|
|
|
|
|
|
Saccades was fun, and effective, but it's time has passed. |
|
|
|
|
|
|
|
|
## 20200622_M |
|
|
## 20200622_M |
|
|
- encapsulated all codedweller in namespace codedweller |
|
|
- encapsulated all codedweller in namespace codedweller |
|
|
- removed all using namespace std |
|
|
- removed all using namespace std |