4 ms·
I see how it can sound appealing to a bureaucrat, but as a programmer, debugging the concurrent evaluation of thousands of "natural" language IF...THEN... rules
by linschn 10y ago
I see how it can sound appealing to a bureaucrat, but as a programmer, debugging the concurrent evaluation of thousands of "natural" language IF...THEN... rules until I find the questionable one where a threshold was defined too low or too high sounds like a nightmare.
- bravo22 10y agoI imagine they would log all the inputs, as well as branches taken so they can later replay everything in a debugger. That would make the process much simpler.
- XorNot 10y agoBeing able to take the blackbox recordings of your combat drone which got shot down, reconstruct the scenario and permute the rules till you get a win, seems like...well, a big win. Air combat is also one of those areas which does notionally have narrowly computable victory parameters - given hardware of capabilities X, there is a model we don't know which should generally predict the outcome.
- rbanffy 10y agoAt least you can actually debug it.
- reitanqild 10y agoOnly if you do it wrong? If it ends up like thousands upon thousands of if statements then you got it wrong (or so I think). Getting it right IMO means realizing that rules are not necessarily source code but often data to be iterated over, filtered etc. This is a form of metaprogramming that can be practiced even in Java ;-)
- PhasmaFelis 10y agoThat would indeed be a nightmare, but trying to debug a machine-generated neural network is actually worse.
- euyyn 10y agoRule-based systems have had for a long time the ability to automatically answer queries about why was such or such decision taken.