CPN Tools demo at Petri nets 2001

If that’s not the CPN Tools demo at the Petri nets conference in June 2001 in Newcastle, I don’t know what is… Featuring: 3D monitor technology and overhead projector. If you look carefully, you can see two mouse cursors. That’s right: multi-input 6 years before the iPhone made it mainstream. […]

Read More… from CPN Tools demo at Petri nets 2001

Nested Transactions and Dining Philosophers

So, here’s an interesting Java issue I came about last week. Java EE supports annotating methods using an @Transactional annotation.  If you’re familiar with it, it’s similar to the synchronized keyword except on the database level.  It also is if you’re not familiar with synchronized. Transactional supports setting how transactions should be picked up – […]

Read More… from Nested Transactions and Dining Philosophers

Is Google’s Go-bot a Breakthrough for Artificial Intelligence?

If you know Betteridge’s Law of Headlines, you immediately know the answer is “no.”  The answer, much like kids, is not really the interesting part however; what is interesting is the process of getting there. Go, like chess and most other games, has been conceptually solved for many years.  So many that I as a […]

Read More… from Is Google’s Go-bot a Breakthrough for Artificial Intelligence?

Improved Paradigm for Analysis, Verification and Data Retention of CPNs using CPNaaS

Design/CPN was the first tool supporting computer-based editing and simulation of colored Petri nets. It was later extended with a for the time powerful state-space analysis tool. CPN Tools improved on Design/CPN by merging the editing and simulation phases, vastly speeding up the modeling phase because simple errors could be found and fixed very quickly. […]

Read More… from Improved Paradigm for Analysis, Verification and Data Retention of CPNs using CPNaaS

Basic Design Principle of CPNaaS

CPNaaS is my new under-development API for colored Petri nets-as-a-service, i.e., a web-API for tools. At the core of the API is a RESTful web-service.  This just means that each resource has a unique URL, which is manipulated as if it were a web-page.  Web-pages are normally just obtained for reading (GET), but may also […]

Read More… from Basic Design Principle of CPNaaS