-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
THF translation is broken #51
Comments
from the line it looks like you may not have set your $SIGMA_HOME environment variable |
Indeed, the recently update of macOS to zsh caused some troubles to me. But after solving the ENVIRONMENT issues, I got:
|
it looks like you may have pointed your $SIGMA_HOME to your $ONTOLOGYPORTAL_GIT and they can't be the same. If you set your environment variables as in the install instructions it will probably solve this. If that isn't it, please delete your catalina.out, restart Tomcat, and send me your catalina.out file and I'll take a look |
Yes, all sumo files are in my
|
yes that is a problem. As per the installation README, you should have a .sigmakee directory in which Sigma keeps copies of the files it displays, and a Git repository (under ~/workspace). If you put them in the same place files can clash during loading and saving. It's a good practice to follow the instructions exactly and be sure everything is working before attempting to change the installation. |
OK, but this doesn't explain why the other transformations are working and only the THF gives me the error:
The #52 fixed it. Regarding now following the instructions, it is good to have some flexibility to allow personal preferences. Since the configuration is based on ENV variables, one should be free to choose the best way to organize the directories. But
It would be nice to have in the documentation something about what actions could change files (and what files) on the disk. I thought that KIF files are only manually edited. If that is the case, I prefer to have KBs as a symbolic link to the SUMO directory. In that way: (1) I don't duplicate files; 2) changes in the KIF are reflected in the SigmaKEE web interface without the need to copy files (OK, maybe I would still need to restart SigmaKEE, bad but not a big problem). Having the KBs symbolic linked to SUMO repository is also good to understand what was touched by SigmaKEE. In my computer, I see that SigmaKEE creates some
|
It looks like the code has some hardcoded path, see
sigma-2-02
that doesn't exist in my system:The text was updated successfully, but these errors were encountered: