-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #27 from Macquarie-MEG-Research/development
Development
- Loading branch information
Showing
39 changed files
with
470 additions
and
56 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,17 @@ | ||
__version__ = '0.9.7' | ||
name = "Biscuit" # noqa | ||
|
||
|
||
def run(): | ||
# main entry point to run the Biscuit GUI | ||
from tkinter import Tk | ||
import os | ||
from os.path import dirname | ||
os.chdir(dirname(__file__)) | ||
|
||
from .Windows import MainWindow | ||
|
||
root = Tk() | ||
|
||
m = MainWindow(master=root) | ||
m.mainloop() |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
function GetReleases() | ||
{ | ||
$.getJSON("https://api.github.com/repos/Macquarie-MEG-Research/Biscuit/releases").done(function (json){ | ||
// most recent release will be first entry in list | ||
var release = json[0]; | ||
if (release.assets.length === 0){ | ||
alert('Something went wrong! Please raise an issue on GitHub!'); | ||
} | ||
var asset = release.assets[0]; | ||
window.location.href = asset.browser_download_url; | ||
}); | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
function GetVersion() | ||
{ | ||
$.getJSON("https://api.github.com/repos/Macquarie-MEG-Research/Biscuit/releases").done(function (json){ | ||
// most recent release will be first entry in list | ||
var release = json[0]; | ||
if (release.assets.length === 0){ | ||
alert('Something went wrong! Please raise an issue on GitHub!'); | ||
} | ||
var version = release.tag_name; | ||
|
||
document.getElementById("complete_link").innerText = "Complete install (" + version + ")"; | ||
document.getElementById("standard_link").innerText = "Standard install (" + version + ")"; | ||
}); | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
{% extends "base.html" %} | ||
|
||
{% block libs %} | ||
{{ super() }} | ||
<script type='text/javascript' src="{{ base_url }}/js/get_version.js"></script> | ||
<script type='text/javascript' src="{{ base_url }}/js/jquery-1.10.2.min.js"></script> | ||
<script type='text/javascript'> | ||
GetVersion(); | ||
</script> | ||
<script type="text/javascript" src="{{ base_url }}/js/download.js"></script> | ||
{% endblock %} | ||
|
||
{% block site_nav %} | ||
{{ super() }} | ||
<ul class="nav navbar-nav"> | ||
<li class="dropdown"> | ||
<a href="#" class="dropdown-toggle" data-toggle="dropdown">Downloads <b class="caret"></b></a> | ||
<ul class="dropdown-menu"> | ||
<li> | ||
<a onclick="GetReleases()" href="#" id="complete_link">Complete install</a> | ||
</li> | ||
<li> | ||
<a onclick="GetReleases()" href="#" id="standard_link">Standard install</a> | ||
</li> | ||
<li> | ||
<a href="https://github.com/Macquarie-MEG-Research/Biscuit">Source code (GitHub)</a> | ||
</li> | ||
{% if page.is_homepage %} | ||
<li> | ||
<a href="installation#complete-install">Not sure which version?</a> | ||
</li> | ||
{% else %} | ||
<li> | ||
<a href="../installation#complete-install">Not sure which version?</a> | ||
</li> | ||
{% endif %} | ||
</ul> | ||
</li> | ||
</ul> | ||
{% endblock %} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
# Converting Elekta data | ||
|
||
Data exported from Elekta MEG machines is stored entirely in a single `.fif` file per run. Because of this all the information required to be added can be entered on one single file. | ||
|
||
## FIF file window | ||
|
||
![fif_initial](images/screenshots/FIF_main_initial.PNG) | ||
|
||
There are a number of fields that need to be completed before the `.fif` file is ready for conversion. | ||
|
||
### Experimental information | ||
|
||
#### Required information | ||
- **Project Name**: ID of the project. This should match the project ID specified in the project settings so that any default values can be applied automatically. | ||
- **Session ID**: Session number with the particular participant. | ||
- **Task**: A shorthand identifier for the task performed. | ||
- **Run**: An integer identifier for the run or block number (often just `1`, `2` etc.). | ||
|
||
#### Subject information | ||
- **Subject ID**: The ID used to identify the participant in a confidential manner. | ||
- **Subject DOB**: The date of birth of the participant. This is entered in *dd/mm/yyy* format (sorry America!). | ||
- **Subject Gender**: One of M (Male), F (Female), U (Unknown). | ||
- **Subject Group**: The group within the study the participant belongs to. THe default values are `Participant` and `Control`, however these can be set in the [project default settings](guide_general.md#settings_window). | ||
|
||
#### Optional information | ||
- **Is empty room**: If this is selected the file is specified as the empty room data. Empty room data is copied to a different location and named based on the date of the recording. You should only select one empty room recoring per day otherwise any other existing empty room recording will be overwritten by the new one. | ||
- **Has empty room**: If this is selected the BIDS data will contain a path pointing to the location of empty room file from the same recording day. Note that there is not check on whether or not this empty room file actually exists as this data can be produced after the BIDS conversion occurs for this file. If you do not have any empty room data that was taken on the same day as this con file, **do not** check this box as the data will not be correct. | ||
|
||
#### Channel name overrides | ||
As Elekta data can contain `BIO` channels which can contain data from `EMG`, `ECG` or `EOG` sources we need some way to specify the data on these channels. | ||
Currently the channel names section will display all channels that have the `BIO` type. | ||
You can rename the channel if you wish, and also specify the type of data on the channel so that the BIDS conversion process can correctly output the right channel type. | ||
|
||
## Exporting the data | ||
When all the required information has been entered, the `Generate BIDS` button will become active. | ||
|
||
![fif_complete](images/screenshots/FIF_main_complete.PNG) | ||
|
||
To export you simply press this button once and a popup will appear which gives the current progress of the export process. | ||
Once the conversion is done the popup will close and the data will available in the `BIDS` folder that will be in the file view. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
# First-time use guide | ||
|
||
At first glance Biscuit may look a little bit daunting to use, but once you are familiar with how it works it is very simple and fast to use. | ||
|
||
### Add new project settings | ||
|
||
If it is your first time using Biscuit to convert some MEG data, you must ensure that the first thing you do before trying to convert any data is to enter the default project settings for your project. | ||
This will allow Biscuit to automatically assign a number of values which saves a lot of time for yourself and can lead to almost automatic exporting, requiring only a few values to be selected. | ||
|
||
To add new project settings you can follow the guide [here](guide_new_proj_settings.md). | ||
It is recommended that you add these settings as soon as you know what they are so that when you take some measurements and open Biscuit for file conversion the data is already added and you do not need to worry about adding them then. | ||
Don't worry if you mess up the settings, they can be changed later and the old file will be overwritten with the new settings. | ||
|
||
### Exporting data to a BIDS compliant folder | ||
|
||
Next, select the folder on the left-hand side that contains the newly acquired data. | ||
|
||
If you have acquired data using a Yokogawa/KIT system, you can proceed to follow the guide specifically for this data [here](guide_kit.md). | ||
If you have acquired data using an Elekta system, the specific guide can be found [here](guide_elekta.md). | ||
|
||
### Copying data off computer (if required) | ||
|
||
The BIDS-compliant data exported by Biscuit will be placed in a sub-folder of a folder named `BIDS`. Depending on your settings it will most likely be placed in a folder named `BIDS-XX` where `XX` is a number. This is to chunk the data so if Biscuit is used on a computer where large amounts of data is being generated, finding the most recent data is easy for those who may need to back up the data. | ||
|
||
To transfer the data off one computer and onto another the easiest way is to use Biscuit's built in file-transfer abilities. This is recommended because it is able to transfer the data in a way that is 'BIDS-safe'. This means that you can transfer the data to another folder containing BIDS-compliant data and the new data will be merged automatically into the file hierarchy. | ||
|
||
Transferring your BIDS-compliant data is as easy as selecting the folder you want to transfer, right-click the folder name in the built-in file browser, then selecting 'Send to...'. | ||
This will display a pop-up which will let you select the location to transfer your files. It is **highly recommnded** that you select the same folder every time you do this. This is most easily achieved by using an external HDD and having a folder on it called `BIDS` (for example). Every time you transfer data off the computer using Biscuit, transfer to this BIDS folder and it will always contain the entire BIDS folder structure of your data. | ||
|
||
*Note*: If you do not see the 'Send to...' option the folder hasn't been specified as a folder containing BIDS formatted data. You can fix this by right-clicking the `BIDS_XX` folder and selecting 'Assign as BIDS folder'. | ||
|
||
### Finishing up | ||
|
||
Now that your data has been "BIDSified", you have an easy to search folder containing all the data from your various experiments. | ||
In the future Biscuit will be able to be used to search this data so that specific tests or recordings can be found easily to allow for easy identification for analysis purposes. |
Oops, something went wrong.