MediaWiki API result

{
    "batchcomplete": "",
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "1": {
                "pageid": 1,
                "ns": 0,
                "title": "Sector 34-ID-C Remote Operation",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "== Remote Connection to 34-ID-C ==\nThe NoMachine server is '''delos.aps.anl.gov'''. We have found that wifi can be flakey and you might see better consistency if you have an ethernet connection.  It's also worthwhile to have a decent monitor or a 4k TV to plug into, but not completely necessary.  4k TVs are <$300 now.\n\nThe following document is detailed instructions for accessing 34-ID-C.\n\n[[media: NoMachine_20210122.pdf |34-ID-C NoMachine setup and use]]\n\n[https://wiki-ext.aps.anl.gov/remoteaccess/index.php/Main_Page APS IT has basic instructions for using NoMachine.]\n\nHere are some hints from APS IT regarding Chrome browser optimizations.  \n\n[[media: ChromeOptimizations.pdf |Chrome Browser optimizations.]]\n\nHere are detailed instructions for using Globus to access your data during your experiment.\nThe APS globus endpoint where your data will be available is APS:DM:34IDC, use your ANL login to access.\n\n[[media: globus_91520.pdf |34-ID-C Globus setup and use]]\n\nThe IT group administrators pay attention to the following email reflector.  If you have problems you can send an email to this address.   But please try to be specific and include as much detail as possible.  CC the beamline staff as well.\n[mailto:[email protected] [email protected]]\n\n[https://nxstatus.xray.aps.anl.gov/nxstatus/ NX server status]\n\nRoss Cell - +1-217-721-5526  Leave a message if he doesn't answer.  Seldom answer unknown numbers.\n\n== Basic Spec at 34-ID-C ==\nCourtesy of Don Walko at 7-ID.  The struck components are not relevant to 34-ID-C.\n\n[[media: Walko spec basics.pdf|Walko Spec basics]]\n\nSpec crystal alignment instructions courtesy of Prof. Ian Robinson.\n\n[[media: IanRSpecNotes.pdf| Ian R. Spec crystal alignment notes]]\n\nAt 34-ID-C we run the sixc version of spec in a screen session for access from multiple terminals on cxd0.\nIf you try to run sixc in a terminal on cxd0 and get a message similar to:\n\n    Can't lock state file \"/net/s34dserv/xorApps/spec/linux-x86/34id/spec.d/sixc/userfiles/epix34id_ttyp#L\".\n    Are you already running on this terminal or another virtual tty?\n\nSpec is already running!  Typically in a \"screen\" session.  Screen allows multiple terminals to connect to a \"screen session\".\ncommands to know are:\n\nThis will display a list of the current screen sessions.\n    cxd0% screen -ls\n    There are screens on:\n        4300.simspec\t(Attached)\n        12243.labtrans\t(Attached)\n        13775.simspec\t(Detached)\n        6123.spec\t(Attached)\n    4 Sockets in /var/run/screen/S-epix34id.\n\nTo attach to one of the existing sessions:\n    cxd0% screen -x spec\n\nYou should see the familiar spec interface. \nIf you want the screen to resize to the window/terminal size enter ctrl-a F\nThen the screen/spec terminal will follow the window size.\n\nIf you wish to create a new screen session, with a custom name like \"spec\" you can run:\n\n    cxd0% screen -S spec\n\nOnly do this if there is not already a screen session called spec when you type screen -ls.  You will see the terminal screen clear and a new prompt appear.  You are now in a separate, attached screen session.\n\nTo detach from any screen session and leave it intact (whatever is running in it keeps running) you press CTRL-a d (control a followed by not control d)\nTo exit a screen session (and kill anything that is running in it), just type exit at the shell prompt.\n\n==Microscope View and Orientation==\nThe image below describes the orientation of the microscope on the diffractometer.  The motor directions specified as \"+ Sample X\" and \"- Sample Y\" are describing the direction the sample will be translated by the motors if the diffractometer angles are at the zero position (th=0, phi=0, chi=90).\n\n[[File: MicroscopeView.jpg]]\n\n==Startup Beamline controls ==\n\n0. Log into the control computer if not already.  The username is cxduser and the password is the standard for the sector.  \n\n1. Start the SSH program.  An Icon is usually on the desktop.  In windows it's SSH Tectia-Terminal, on a mac you just open a Terminal. \n   Windows:\n   Click Quick Connect button on the SSH tool bar.\n   The default should be to log into cxd0.xray.aps.anl.gov\n   The default user should be cxduser\n   Please don't write the password in publicly available documents (google docs etc.).\n   Mac:\n   Type on the command line of a terminal:\n     ssh -X cxduser@cxd0\n  \n2.  On Windows you will need to ensure that the X server is running.  An icon called Exceed should be on the desktop.  If it is already running there will be an icon on the taskbar that looks like and X wearing a top hat.  Don't ask me why the X is wearing a top hat.\n\n3.  At the cxd0 prompt type cxdusermenu and press enter/return.\n    -bash-4.2% cxdusermenu\n\n4.  A small grey controls window should appear on one of the screens.  Click the left most menu that says Control and select the 34ID-C mainscreen menu option.  You should see the familiar control window for the beamline.\n\nAlternatively, there are icons on the windows desktop that will open the main control screen or the cxdusermenu.  Hopefully they continue to work after IT updates things.\n\n\n== Random Fixes ==\n\n  '''Terminal with Spec is frozen'''\n  Occasionally the ssh terminal running spec will get a bad key combination and freeze.  Sometimes pushing CTRL-q (maybe Q) will unfreeze it.  The keys that cause it to freeze is CTRL-s.  \n\n  '''Motor frozen in Moving State'''\n  Click the More button on the motor control.\n  Select the (All) option from the drop down menu in the top left of the More screen.\n  On the right, about 1/3 down, in the All screen there is a drop down that says Go.  Click that and select Stop.  Then click again and select Go.\n  This should have cleared the motor stuck in moving state.  Close the More and More all screens if you want.\n  Don't mess with the soft limits unless you tell beamline staff.\n\n  '''Theta motor doesn't work and readback is different than set value'''\n  Click the More button on the motor control.\n  Select the All option from the drop down menu in the top left of the More screen.\n  At the bottom right there is a Torque control.  Set it to enable.\n  Now adjust the set point in the motor control to match the readback.\n  This happens because the cables that are either inside the stage stack or hanging from the side get snagged.  Try to keep an eye on them with the camera and let staff know if we need to go in and rearrange them.\n\n==Beamline Calendars==\n\nIf you care about the 34-ID-C schedule.  These files are available externally to APS, so you can add them to Google or whatever you like.\n      A new version of the Beamline Scheduling application will be released\n      tomorrow (6/25/2013).  This will be version 2-20-0.  Work on the internal\n      server will start at 10AM.  Work on the external server will start at 1PM.\n      Changes in this version will include:\n\n     - Additional iCal (.ics) files will be produced automatically. These files\n     will solve the problem that all iCal files presently contain a copy\n     of the run schedule.  This produces clutter on calendars where\n     individuals would like to display more than one beamline.  The calendars\n     files are stored in the usual location:\n         https://schedule.aps.anl.gov/schedules/\n     The original calendar files have file names similar to the beamline name\n     shown in the Schedule System (i.e 34-ID-C.ics).  For beamlines that\n     contain characters that cannot be used in filenames (such as a comma)\n     those characters become an underscore (e.g. 6-ID-B,C goes to 6-ID-B_C.ics).\n     New files that will be created include the following:\n        - Append _brief (such as 34-ID-C_brief.ics) contain the same\n          information as the original files with no run schedule or staff\n          support information.\n        - Append _staff (such as 34-ID-C_staff.ics) contain only the staff\n          support information.\n        - runSchedule.ics contains information about the run schedule only.\n        - runSchedule_brief.ics  This reduces shutdown and machine\n          studies periods to show only the first and last days.\n\n== FCC crystal Model ==\n\nIf you install eDrawings from Dassault you will be able to open the 3D model of our little FCC model at the beamline.\n\n[https://www.edrawingsviewer.com/ '''eDrawings Viewer''']\n\nThen download this file.  Right click and \"save file as\"\n\n[[Media:FCC_crystalfaces.easm]]\n\nIf you don't want to install eDrawings and download the easm file you can download this HTML and double click on it.  It should open in a browser with in integrated viewer to display the model.  For some reason the wiki server doesn't like to serve HTML files with code in them.  Right click on the link below and save the file to your desktop.\n\n[https://wiki-ext.aps.anl.gov/s34idcremoteoperation/images/9/98/Cube1.html HTML 3D model file]\n\n== Phasing on Sayre ==\n\nThis is how you run phasing programs on sayre.xray.aps.anl.gov\n\nConnect to the beamline Mac (cxd2.xray.aps.anl.gov). It should be available to you through delos.aps.anl.gov, so just follow the instructions above regarding connecting to the beamline computers.  But select cxd2 instead of cxd3 as described.\n\nOnce connected to the Mac (cxd2), open a terminal window and type sayre at the prompt.  This will connect you to the gpu machine at APS.  \n\nActivate cohere environment and go to bin directory using the commands below:\n\n    conda activate cohere\n\nRefer to Cohere documentation at https://cohere.readthedocs.io/en/latest/ for more information.\n\nThe documentation below for using the GUI and command line is also applicable to phasing on Sayre.\n\n== Paraview on CXD0 ==\n\nWhen logged into cxd0 through nomachine you are connected as your username.\nThere are a couple of things you can do.  \n\n\n1. Change to the beamline user.\n    type at the bash prompt su cxduser  \n    bash-4.2$ su cxduser\n    enter the standard user password\n    Now everything on the command line should look like it does when logged in as cxduser.\n    Paraview is kept in \n    34idc-work/2022/ParaView-5.10.1-MPI-Linux-Python3.9-x86_64/bin\n    so you could now type\n    /34idc-work/2022/ParaView-5.10.1-MPI-Linux-Python3.9-x86_64/bin/paraview\n    and it should pop up on the screen.\n\n2. create a link to the paraview installation and just run it as yourself\n    ln -s /net/s34data/export/34idc-work/2022/ParaView-5.10.1-MPI-Linux-Python3.9-x86_64/bin/paraview paraview\n    then run it\n    ./paraview\n    from your home dir.\n\n3. use paraview as cxduser on sayre\n    ssh cxduser@sayre\n    log in with usual password\n    run paraview\n    /34idc-work/2022/ParaView-5.10.1-MPI-Linux-Python3.9-x86_64/bin/paraview\n    This may be a little slower since it is running on sayre and displaying on cxd0\n    I don't know what it will do to your phasing memory on the sayre graphics cards either.\n\n== Installing and use of phasing programs on your computer ==\n\n1.[https://cohere.readthedocs.io/en/latest/installation.html Conda installation instruction]\n\n2.[https://github.com/AdvancedPhotonSource/cohere Github source code]\n\n2.5 [https://github.com/AdvancedPhotonSource/cohere-scripts Github User Scripts code]\n\n3.[[Media:Install_scripts.pdf | Installing users scripts]]\n\n4.[[Media:Using_cohere_GUI.pdf | Using GUI to run the phasing programs]]\n\n5.[[Media:Using_cl_scripts.pdf | Using command line scripts to run the phasing programs]]"
                    }
                ]
            }
        }
    }
}