v1.0.0

usage

this has changed since the last release, PLEASE READ

1. create a folder called idslabel-v1
2. place the idslabel executable you download from this page into that folder.
   • if you're running idslabel as a script from the command line, the folder it's already in is good enough, no need for a new folder
3. copy your lab's config.json file into that folder
   • if you're running idslabel as a script from the command line, copy the config.json into the folder that contains the idslabel.py file. DO NOT separate the idslabel.py file from the other .py files in this folder. All the .py files need to be in this folder.
   • make sure the config.json has 092616 in the filename. This is the date the config.json was made. It's the latest thus far.
4. create another folder and call it idslabel_blocks.
   • this will be your clips directory. DO NOT move or delete anything in this folder. This is where idslabel will download blocks and load them from. It will delete blocks when you're done with them, so no need to worry about filling up hard drive space. Let idslabel deal with everything in this folder.
5. If you're using the executable, double click it to start the program.
   • if you're running the script from the command line, run: $: python idslabel.py
     from the command line, within the idslabel directory which contains all the source code.
6. Type your name into the CODER_NAME box and press enter.
   • it will ask you to set the clips directory.
   • navigate to the idslabel_blocks folder you originally created in step 4, and choose that
   • idslabel will load the config.json file that you placed alongside the executable in step 3.
   • if you've never used this name before it'll say that the server doesn't recognize this user as belonging to that lab, and that you should add it by going to File -> Add User to Server
     • do that
7. You should be ready to go. The rest of the usage is the same as before. There are a bunch of new features though, listed below.

note

The server is now hosted in Merced, California, so it might take considerably longer for blocks to reach you when you request them (and basically every other network operation in idslabel). Here in Durham, NC it takes 6-10 seconds to get a group of 3 blocks.

new features

• delete block submission (on Get Lab Info page)
  • You can pick a specific instance of a specific block submission to delete from the server.
• delete all of a specific user's blocks (on Get Lab Info page)
  • This will delete all the submissions in the database that were submitted by that specific user.
• delete all the blocks submitted by the whole lab (on Get Lab Info page)
  • This will delete all the submissions in the database that were submitted by any member of the currently logged-in lab (i.e. currently loaded config.json)
• delete a user's account (on Get Lab Info page)
  • This will delete the user and all their submitted blocks from the server. The username will be removed from membership with the lab. It can always be added again with File -> Add User to Server, but the deleted blocks cannot be recovered.
• choose specific block to pull down (on Get Blocks page)
  • File -> Choose Blocks from Server
    • Double click on the blocks you want in order to select them, then click "Get Blocks"
• view all the instances of submissions of a single block
  • a user might have submitted more than one instance of labels of a single block. Each of these attempts is individually viewable in the Get Lab Info page.
• look for config.json in the current working directory
  • if there's a single config.json in the same directory/folder as the executable, then it will use this config file and not ask you to specify it
  • you can now also switch your config.json by loading a new one from the File menu. ("Load config.json File)
• get more specific information about a user from the Get Lab Info page by double clicking on a username, for example:
  • total # blocks submitted

  • training blocks submitted

  • reliability blocks submitted