Find information on common issues.
Ask questions and find answers from other users.
Suggest a new site feature or improvement.
Check on status of your tickets.
15 Jun 2016
This is to let you know that the 'Datafeeder's Guide to Aggregation' is now available for download from the IELab Forum's 'Resources' area (https://ielab.info/groups/forum/resources).
28 Feb 2017
The Satellite Data Feeds manual (by Joe Lane and Arne Geshke) is now uploaded to the resources area of the Forum, listed under "training materials" and with tags of "datafeeds" and "indicators" see https://ielab.info/groups/forum/resources
18 Mar 2017
Hello IO hive mind
We are updating the 2007 IRIO tables for China for 2012. The official tables won't be released for some time so we are updating the tables ourselves to do some analysis on CO2 emissions.
Many people have used the gravity model to update IO tables, but there are many different variants of this method and it has been applied inconsistently - obviously leading to very different end results. There does not appear to be any consensus on the 'right' coefficients or values to use in a gravity model (i.e. distance, travel time, weights for exponents etc)
My favoured approach at this steage is to use the 2007 matrix as an initial condition and then use the RAS technique to update the table using total output values for 2012. My assumption here is that the best guess at what a table looks like in 2012 will be the previous known table, which was 2007. The gravity model appears to throw out prior information on the structure of the table in favour of the theory that regions that are closest trade the most.
What are your thoughts, does my much simpler method of using the 2007 IO tables as an initial condition and then update this table using the RAS method for the new sectoral outputs for 2012 hold water?
If you know of any relevant literature where these methods are compared that would be very helpful!
12 Jul 2017
this is to let you know that we now have master documents for the different manuals that were written for the MRIOLab Suite. So far, we had a collection of different documents that covered the various aspects such as data feed coding, concordance handling, satellite feeds etc. We have brought these different documents together into two master documents:
1. "MRIOLab Suite - CreateBaseTable GUI Manual". This manual is intended for users who are primarily using the Matlab GUI "CreateBaseTable" to build base tables. The manual covers the use of the GUI, how to find and load the final MRIOs, and how to build your own aggregators.
2. "MRIOLab Suite - Data Feed Developer Manual". In this manual we brought together the various different manuals that were written over the past few years on topics that are related to developing data feeds. There are also some introductory sections on how to execute data feeds (a topic that had not been covered anywhere previously). This manual - in combination with the Aisha manual - will serve as the sole reference point for data feed development.
Note: These two manuals replace all previously available documents. Previous documents will not be supported anymore, and these two documents serve as the resource of information on how to work with the MRIOLab Suite software. If you have additional manuals on using the CreateBaseTable GUI and/or how to develop data feeds, please get in touch with me so that I can add these sections one of these two documents.
The documents are available in the resource section of this hub site.
20 Mar 2018
this is to let you know that as of today, we have moved all AusIELab development to the UNSW servers. The USyd copy of the AusIELab root will be a mirror of the UNSW version. That means: If you add something at UNSW, it will be added at USyd, if you delete something at UNSW, it will be deleted at USyd. Most importantly: If you add something at USyd (which you are not supposed to do), but not at UNSW, it will be deleted almost instantly, because it does not match the UNSW version.
The USyd version of the AusIELab is set to read-only permissions. Hence, you can also NOT execute data feeds at USyd. The only functionality to remain at USyd is to build base tables.
The sync between UNSW and USyd is set to every five minutes.
Also, I have disconnected the USyd code directories datafeeds_code and IEfeeds_code from the git repository. The UNSW versions of these directories and still managed through git, since UNSW is the only place where code changes should be happen.
22 Mar 2018
as you may know, the AusIELab by default produces MRIO that have 18 different sheets. Hardly anybody (if anybody at all) uses anything else than the basic price sheet. We do however need to process the data for the remaining 17 sheets, which is computationally significant, and which extends the runtimes of the tables builds.
We have there introduced a new feature. By default, every AusIELab MRIO is now produced with five sheets only. These five sheets are simply an aggregation of the 18 previous sheets. The sheet labels for the new five sheets are
Currently, you can only revert to the old workflow and produce MRIO with 18 sheets if you start your run through the Matlab interface. All web-interface MRIOs are built five these five sheets only.
In the Matlab interface, you can deactivate the option "Aggregate sheets using default aggregator" in the settings menu if you want to return to 18 sheets.