Getting Started With ResearchCyc - Revision history

DavidWhitten: /* Installation */

2019-05-29T22:24:53Z

‎Installation

DavidWhitten: /* Installation */

2019-05-29T22:23:32Z

‎Installation

DavidWhitten: /* Installation */

2019-05-29T22:23:04Z

‎Installation

DavidWhitten: /* Installation */

2019-05-29T22:20:16Z

‎Installation

DavidWhitten: /* 7. Create Cyclist Account */

2019-05-29T22:19:00Z

‎7. Create Cyclist Account

DavidWhitten: /* 7. Create Cyclist Account */

2019-05-29T22:18:20Z

‎7. Create Cyclist Account

DavidWhitten: /* 6. Try Test Launch */

2019-05-29T22:17:59Z

‎6. Try Test Launch

DavidWhitten: /* 1. Configuring the host machine… */

2019-05-29T22:16:46Z

‎1. Configuring the host machine…

DavidWhitten: /* 1. Configuring the host machine… */

2019-05-29T22:14:44Z

‎1. Configuring the host machine…

DavidWhitten: /* 1. Configuring the host machine… */

2019-05-29T22:09:53Z

‎1. Configuring the host machine…

@@ Line 36: / Line 36: @@
   I recommend installing on a publicly-accessible server, say, on an Amazon Web Services (AWS) Elastic Compute Cloud (EC2) instance. Doing so will allow you access from any browser if your local machine doesn’t accept requests on port 80.
   For example, this is what it looks like in Chrome on a Samsung Note 2…
-  [[File:Rcyc-viewed-on-samsung-note-2-168x300.png|672px]]
+  [[File:Rcyc-viewed-on-samsung-note-2-168x300.png|upright=2.0|Rcyc Page]]
 === 1.  Configuring the host machine… ===

@@ Line 36: / Line 36: @@
   I recommend installing on a publicly-accessible server, say, on an Amazon Web Services (AWS) Elastic Compute Cloud (EC2) instance. Doing so will allow you access from any browser if your local machine doesn’t accept requests on port 80.
   For example, this is what it looks like in Chrome on a Samsung Note 2…
-  [[File:Rcyc-viewed-on-samsung-note-2-168x300.png|336px]]
+  [[File:Rcyc-viewed-on-samsung-note-2-168x300.png|672px]]
 === 1.  Configuring the host machine… ===

@@ Line 36: / Line 36: @@
   I recommend installing on a publicly-accessible server, say, on an Amazon Web Services (AWS) Elastic Compute Cloud (EC2) instance. Doing so will allow you access from any browser if your local machine doesn’t accept requests on port 80.
   For example, this is what it looks like in Chrome on a Samsung Note 2…
-  [[File:Rcyc-viewed-on-samsung-note-2-168x300.png|100%]]
+  [[File:Rcyc-viewed-on-samsung-note-2-168x300.png|336px]]
 === 1.  Configuring the host machine… ===

@@ Line 36: / Line 36: @@
   I recommend installing on a publicly-accessible server, say, on an Amazon Web Services (AWS) Elastic Compute Cloud (EC2) instance. Doing so will allow you access from any browser if your local machine doesn’t accept requests on port 80.
   For example, this is what it looks like in Chrome on a Samsung Note 2…
-  [[File:Rcyc-viewed-on-samsung-note-2-168x300.png]]
+  [[File:Rcyc-viewed-on-samsung-note-2-168x300.png|100%]]
 === 1.  Configuring the host machine… ===

@@ Line 182: / Line 182: @@
       d.   You should be in a new frame that says “Unknown Cyclist…Do you want to create a new Cyc constant with this name?”. Click “Yes, Create Cyclist”.
                  Note: On at least one occasion, the RCyc server quit after this command, returning no content to my browser and showing this in the terminal:
-−
          CYC(1): ./bin/cyc-runner.sh: line 298:  2555 Killed                  java ${BIT_FLAG} ${SERVER_FLAG} -Xms${MIN_HEAP} -Xmx${MAX_HEAP} ${OLD_SORT_FLAG} ${CODE_CACHE_FLAG} ${PERM_SIZE_FLAG} ${EA_FLAG} ${CM_FLAG} ${PGC_FLAG} ${FAST_OPTS_FLAG} ${AGENT_LIB_FLAG} ${EXTRA_OPTIONS} ${CYC_JAVA_OPTIONS} ${LOG_FLAG} ${ASSERTS_FLAG} -cp "${CLASSPATH}" ${MAIN_CLASS} -f "${INIT_FORM}" "$@"
          Shutting down Derby which provides the SCG repository ....

@@ Line 173: / Line 173: @@
   If you’re going to edit any rcyc content, and you probably will eventually want to, you’ll need to create an account other than the default Guest account to do so.
       a.   Check researchcyc-4.0o/server/cyc/run/init/release-specific-init.lisp to make sure the following is NOT present there.
-−
          (noting-progress "Enabling password authentication"
             (csetq *image-requires-authentication?* T))
-−
            If it’s present, delete it and restart the RCyc server. One way to stop the server is to enter (exit) (a SubL command) at the CYC: prompt; another way is to reboot the Ubuntu server.
       b.   On the start page, there’s a textbox for entering a userid to change which user is logged in. Enter “CycAdministrator” and Submit.

@@ Line 136: / Line 136: @@
          If you get error <code>bash no such file or directory executable</code>
          then one possibility is that Windows line-endings made it into some of the text files; try:
-−
          sudo apt-get install dos2unix
          researchcyc-4.0o$ find . *.* |xargs dos2unix
          chmod a+x ./bin/*.sh
          sudo apt-get install openjdk-7-jre-headless
-−
          (My initial research into this problem suggested that there might be 32-bit components in rcyc that wouldn’t run in Ubuntu 13.10 without ia32-libs but that turned out to be a red herring.)
@@ Line 154: / Line 154: @@
          Running on: ubuntu
          OS: Linux 3.11.0-13-generic (amd64)
-−
       c. and after another five minutes, you should see:

@@ Line 65: / Line 65: @@
                  http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/putty.html#putty-private-key
          xii.   To upload rcyc, do something like this:
-−
-               <code> C:\Windows\system32>C:\”Program Files (x86)”\PuTTY\pscp.exe -r -i C:\[your path]\[your private key file].ppk “C:\[another local path]\researchcyc-4.0o\*.*” ubuntu@[your ec2 public dns]: </code>
+             <code> C:\Windows\system32>C:\”Program Files (x86)”\PuTTY\pscp.exe -r -i C:\[your path]\[your private key file].ppk “C:\[another local path]\researchcyc-4.0o\*.*” ubuntu@[your ec2 public dns]: </code>
-−
                I would have preferred WinSCP’s graphical UI, but it kept showing connection errors
                 while transferring large files. If pscp is interrupted, you can re-run the command above.
@@ Line 116: / Line 116: @@
               l.   If you haven’t already unpacked the RCyc gzipped tar file, do so now,
                      like this: <code> tar -xvzf *.tgz </code>
-−
              The remainder of the instructions will assume your terminal’s working directory is this one.
-. ResearchCyc’s scripting language is a [[Lisp]] variant called [[SubL]] that runs on top of Java.
+:: 4. ResearchCyc’s scripting language is a [[Lisp]] variant called [[SubL]] that runs on top of Java.
               So, to install Java in your vm, open a terminal there and
                 <code> sudo apt-get install openjdk-7-jre-headless </code>

@@ Line 52: / Line 52: @@
                 c.  In the right pane, select the row of the instance’s security group
                 d.  In the bottom pane, select the Inbound tab.
-                     To allow requests from all IP addresses, there should be a row with Port=22 and Source=0.0.0.0/0. '''Be sure to add Port=3602 and Source=0.0.0.0/0 because rcyc’s webserver uses this port.'''
+                     To allow requests from all IP addresses, there should be a row with Port=22
-                e.  For more guidance, see http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/authorizing-access-to-an-instance.html
+                    and Source=0.0.0.0/0. '''Be sure to add Port=3602 and Source=0.0.0.0/0 because
           vii. If prompted, click “Yes, I want to continue with this instance type” (It won’t be free)
          viii. Click Launch
-          ix.  Choose an existing key pair, or create a new one (and be sure to download the key pair file). Then click “Launch Instances”.
+          ix.  Choose an existing key pair, or create a new one (and be sure to download the key pair file).
           x.   Make sure you’ve installed Putty
-         xi.   To convert the pem file to Putty’s ppk format, follow http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/putty.html#putty-private-key
+         xi.   To convert the pem file to Putty’s ppk format, follow
          xii.   To upload rcyc, do something like this:
-                C:\Windows\system32>C:\”Program Files (x86)”\PuTTY\pscp.exe -r -i C:\[your path]\[your private key file].ppk “C:\[another local path]\researchcyc-4.0o\*.*” ubuntu@[your ec2 public dns]:
+               <code> C:\Windows\system32>C:\”Program Files (x86)”\PuTTY\pscp.exe -r -i C:\[your path]\[your private key file].ppk “C:\[another local path]\researchcyc-4.0o\*.*” ubuntu@[your ec2 public dns]: </code>
-               I would have preferred WinSCP’s graphical UI, but it kept showing connection errors while transferring large files. If pscp is interrupted, you can re-run the command above. If you decided to upload the gzip instead of unpacking first, or you didn’t set the persistent storage high enough, and then find that you don’t have enough free disk space to unpack (type df -h to check), there is a way to increase disk space without having to lose your disk content
+               I would have preferred WinSCP’s graphical UI, but it kept showing connection errors
         xiii.   Configure Putty to make it easier to login to the server for future maintenance…
              a.  In Windows, go to Start | Putty
@@ Line 71: / Line 80: @@
              e.  Window | Columns = 120
              f.  Window | LinesOfScrollback = 2000
-             g.  Session | SavedSessions = “rcyc”, then click Save. When you attempt an ssh connection with this EC2 instance in the future, you can select “rcyc” in the sessions list, click Load, and then edit the host address to match what the ec2 console shows.
+             g.  Session | SavedSessions = “rcyc”, then click Save.
              h.  Before clicking Open to start the ssh session, you might need to change to a network that doesn’t block port 22.
              i.  When prompted “The server’s host key is not cached in the registry…”, click Yes.
@@ Line 89: / Line 100: @@
      B. Otherwise, if you prefer installing locally…
-.  Let’s take the hard case of using Windows. The rcyc setup instructions indicate some features aren’t supported on Windows, so I setup Ubuntu 13 64-bit in VMWare Player 6 on Windows 7 Pro 64-bit. But before creating that virtual machine, go into your BIOS and ensure that “Intel Virtualization Technology” (i.e., “Intel VT-x”) is enabled; if there is another setting limiting use of VT-x to “trusted” applications, turn that off.
+:: 1.  Let’s take the hard case of using Windows. The rcyc setup instructions indicate some features aren’t supported on Windows, so I setup Ubuntu 13 64-bit in VMWare Player 6 on Windows 7 Pro 64-bit. But before creating that virtual machine, go into your BIOS and ensure that “Intel Virtualization Technology” (i.e., “Intel VT-x”) is enabled; if there is another setting limiting use of VT-x to “trusted” applications, turn that off.
-.  Before powering-on the Ubuntu VM, make sure its Memory setting is at least 7680MB.
+:: 2.  Before powering-on the Ubuntu VM, make sure its Memory setting is at least 7680MB.
-.  To allow fast transfer of files with the Windows host, I created a “forUbuntu” folder on my Windows desktop, moved the unpacked download contents there, installed VMWare Tools in the vm, and set the vm option for Shared Folders to the new one on my host desktop. Now access the shared folder in the vm and copy the files to a local folder in the guest Ubuntu filesystem.
+:: 3.  To allow fast transfer of files with the Windows host, I created a “forUbuntu” folder on my Windows desktop, moved the unpacked download contents there, installed VMWare Tools in the vm, and set the vm option for Shared Folders to the new one on my host desktop. Now access the shared folder in the vm and copy the files to a local folder in the guest Ubuntu filesystem.
               a.   sudo apt-get install build-essential
               b.   sudo apt-get install linux-headers-`uname -r`