even better more structured throughput scheduling

plot adjustments
validation adjustments

docs/evaluation/pimcomp-reproducibility.md

@@ -43,10 +43,13 @@ shows why a fusion label is not proof of numeric equivalence.
 
 Pimsim accepts ISA instructions rather than ONNX operators. Its
 [instruction decoder](../../backend-simulators/pim/pimsim-nn/src/isa/Instruction.cpp)
-rejects `vsoftmax` (opcode 21) and unknown opcodes; unsupported operations must
-not be approximated in the oracle. This is why the dedicated GoogLeNet artifact
-removes LRN/Softmax and the YOLO artifact removes Softmax. YOLO retains its other
-operations, including MatMul/Transpose and detection decoding, for Raptor.
+omits `vsoftmax` (binary opcode 21) before fetch and warns once per process
+because it has no timing model. Other unknown opcodes remain errors.
+Reported timing and energy exclude Softmax work. Functional validation still
+executes Softmax. The comparison uses full YOLO and GoogLeNet with only its two
+LRN nodes bypassed. VGG8 and both ResNet graphs retain all operators.
+The historical `*-pimsim-nn.onnx` files retain the earlier Softmax-free graphs
+for result reproduction; they are no longer the suite's selected inputs.
 
 ## Standalone frontend/backend reproduction