Over the years, I have received feedback that the name *QANUS* doesn’t have a nice ring to it. I appreciate your suggestions and decided to rename the project to “NUS Open QA”. As part of this change, I am also dropping the use of the domain name (qanus.com), and will be hosting this project at (junping.ng/nusopenqa) instead. Do bear with out-dated references throughout the site during this transition. Thanks!
Category Archives: Updates
There is currently an outage with the web server hosting the QANUS distributable.
In the interim, I have set up a temporary mirror in case you like to download QANUS. If you face any problems downloading the distributable from this new mirror, do drop me a mail!
The new download links are already updated in the Download page. Thanks!
There is an update to the QANUS distributable (v29Nov2012). The previous version (v23Apr2011) made use of a web service for named entity recognition (NER). However the NER service wasn’t always reliable, and this prevented many people who had downloaded QANUS from using it out-of-the-box.
To remedy the problem, the new distributable is shipped and configured with a local NER engine (Stanford NER). Users who download the package should now be able to follow the instructions on the README file and run QANUS out-of-the-box.
We have switched over successfully to a new web server. The new server should be able to deliver this site more quickly.
Meanwhile, we are hoping to be able to release another version of QANUS soon which does not require any external libraries or web services. The current release makes use of a named-entity recognition web service hosted on the servers of my research group. However load issues have affected the reliability of the web service. The planned release will hopefully make it easier for everyone to run QANUS straight “out-of-the-box”.
The official page for QANUS is currently being moved over to a new server.
During this transition phase, there may be some duplicated or un-synchronised content between the old and new web hosts. We apologise for this.
Once the transition is complete, these issues would hopefully be resolved. Thank you for your understanding!