sp
/
GSW_AI_LAB
Archived
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
The source code and dockerfile for the GSW2024 AI Lab.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
This repo is archived. You can view files and clone it, but cannot push or open issues/pull-requests.
3 Commits
1 Branch
0 Tags
27 MiB
Tree: e33ef1f8f2
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'e33ef1f8f2'
${ noResults }
GSW_AI_LAB/tempest-devel/resources/3rdparty/cudd-3.0.0/dddmp/README.testdddmp

79 lines
2.2 KiB
Raw Normal View History

initial commit
4 weeks ago
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
  1. README file for the test program of the DDDMP-2.0 package
  2. Revision: Version 2.0.2, February 01, 2004
  6. WHAT IS TESTDDDMP
  7. =================
  9. testdddmp is a test program for the dddmp package.
  10. Practically, it is a naive user interface to load, store and execute
  11. operations with BDDs.
  12. It is included to provide a sanity check for the installation of the
  13. package and an easy tool to play with BDDs and BDD on files.
  17. MAKE TESTDDDMP
  18. ==============
  20. Run "make testdddmp".
  21. This should produce the testdddmp executable file.
  25. TEST DDDMP
  26. ==========
  28. Run the runAllTest.script file in the exp directory.
  29. This should run all the test?.script files in the same directory.
  30. Each of them is specifically written to check a particular feature of
  31. the package (e.g., store and load of BDDs, store of CNF formulas and
  32. retrieval, etc.).
  33. Each test?.script should terminate with a comparison with a previously
  34. generated set of files, then with the following set of messages:
  36. Files 0or1.bdd and 0or1.bdd2 are identical
  37. Files 2and3.bdd and 2and3.bdd2 are identical
  38. ...
  40. If so everything is OK.
  42. Notice that mismatches may be caused by the presence of CR - LF characters at
  43. the end of each BDD file line.
  47. WORK WITH DDDMPTEST
  48. ===================
  50. To work with dddmptest (once the executable file has been built) it is enough
  51. to run it (no parameter is necessary).
  52. The help command print out the main commands available.
  53. For each command further inputs are eventually required on an interactive
  54. basis.
  55. BDDs and ADDs can be loaded from files by choosing the file name or they
  56. can be directly created (randomly for example).
  57. They can be maintained into the main memory trough an array of BDD pointers.
  58. Operations (logical and re-ordering) can be performed on any BDD into this
  59. array.
  60. Eventually any of them can be stored in a file giving the file name.
  61. BDDs can also be stored in a CNF format using three different possible
  62. solution to store them.
  66. FEEDBACK
  67. ========
  69. Send feedback to:
  71. Gianpiero Cabodi and Stefano Quer
  72. Politecnico di Torino
  73. Dip. Automatica e Informatica
  74. C.so Duca degli Abruzzi 24
  75. I-10129 Torino
  76. Italy
  77. E-mail: {gianpiero.cabodi,stefano.quer}@polito.it
  78. WEB page: http://staff.polito.it/{gianpiero.cabodi,stefano.quer}