edggy / pylemma Goto Github PK

The website should have a text editor for creating the proofs

Previous criticisms pointed out that MySQL has flaws, which should have an analysis of whether to move over to another DBMS such as MongoDB, Postgres, etc.

Since proofs follow a very similar structure so the files can have a specialized compression

This project needs a homework server for grading the proofs

The server part and database system part were finished by different developers. So in the next month, I will try to combine them together. Both of them are written by python. So I think this work is not so hard! I need to know what happen in the server part and then I can write the code to connect them. The server get the homework file include name, RIN. The server will send to the database. Database system will record these kind of the data.

The website should have some means of verifying proofs, either through having the verification server code integrated with the website or through some api calls.

The team needs to create a plan for what stack/frameworks will be used for creating the website. The website will feature both a proof creator app and a connection to the verification server.

Some means of showing that the server was able to verify/disprove a proof without the server getting the main contents of the proof

The use of generalized inference rules would be very helpful.

Example 1:

and(A, B, C, D, E, F)
#---------------------
and(B, D, E)

Example 2:

or(A, B, C)
|-(A, S)
|-(B, S)
|-(C, S)
#-----------
S

This project seems to be involving several parts:
1) The formal logic structure
2) A verification server
3) A client UI for creating proofs
4) A website for both creating and verifying proofs

These things seem to be very distinct, so maybe separate repositories rather than different branches should be made.

The website and client should have similar UIs for creating proofs, so a port of the interface should be done

Might be a good idea to allow for importing specific subproofs from proof files

With the inclusion of a website, there exists a need for multiple databases. The website will need a database while the verification server database schema was criticized previously and should be re-examined (and potentially redesigned) to address such concerns. In particular, unnecessary attributes and foreign keys/tables should be removed.

Use Tkinter to crate a rough layout for the front-end UI. Could be similar to Fitch.

Traceback (most recent call last):
File "main.py", line 80, in
tstPrf = parsers.defaultProofParser(filename)
File "/home/jacobn2/Dropbox/PyLemma/PyLemma/pyLemma/parsers.py", line 623, in defaultProofParser
for n, line in enumerate(string.split('\n')):
AttributeError: 'tuple' object has no attribute 'split'