Monday, 17 June 2013

InterPro is temporarily reverted to v42.0

An update on our progress.  We decided to revert the InterPro website back to the previous release's data (v42.0).  This means that the Pfam release that was incorporated into release v43.0 is no longer visible via the website, at least, until the fix is completed.  The full status of all our services is now as follows:

InterPro website

Currently displays v42.0 data - all protein match information visible on the site is now correct and can be used with confidence.  The version of Pfam that is visible is v26.0, however.

InterProScan5 (downloadable)

The InterProScan5 current version (RC6) was built against v42.0.  We hadn't built and distributed the version (RC7) that was for v43.0 of the data and so users are still safe using InterProScan5 RC6.

InterProScan4 (downloadable)

Standalone InterProScan4 (downloadable from our FTP site) had data released for v43.0 which included Pfam 27.0, however, it was only the match_complete.xml file that was affected by the data.  Users could either run their InterProScan4 installation with 43.0 data with the -nocrc option on the command-line or can download the data for release 42.0 from the FTP site ( and and revert back to that version.

InterProScan4 (EBI-hosted)

InterProScan4 is currently running using InterPro release 42.0 data and can therefore be used with confidence.  The version of Pfam included is v26.0.

Next steps

We will hopefully make a new public release next week which will contain Pfam 27.0 and correct protein match information to the website.  Updates to InterProScan v4 data and InterProScan 5 (RC7) will follow shortly afterwards.  These updates will be announced on the twitter feed and mailing lists as v43.1

Again, many thanks for your patience whilst we sort out these issues.

Friday, 14 June 2013

Update on fix to InterPro 43.0

We're still working on fixing release 43.0 and we are aiming to release a fixed version (v43.1) next week.  We're sorry it's taking so long to sort out but we are working hard to do so.  It's highly likely we'll temporarily revert the public data to release 42.0 if we've not fixed 43 by Monday.


We have had some questions about the use of InterProScan

Users of InterProScan v5 will be pleased to know that we noticed the problem with 43.0 before we had updated I5, therefore, all the data coming from InterProScan 5 should be correct and you can use it with confidence.

InterProScan4, however, is affected by this problem if you have not used "-nocrc" option on the commandline of the standalone version, or if you have used the EBI-hosted version without specifying "-nocrc".   Running InterProScan 4 with the lookup disabled (using "-nocrc") will not use the problemmatic dataset, and so the results should be OK.

Once again, we apologise for any inconvenience this might have caused our users.

Monday, 10 June 2013

Problem with InterPro release 43.0

For the first time, we've discovered a major problem with the match data generated for InterPro.

This has resulted in incorrect InterPro calculations for approximately 3 million protein sequences in the UniParc database - therefore, it is highly likely that a number of UniProtKB proteins will have incorrect match data visible in the InterPro web interface.  At the same time, we have noticed that some of the pathway mappings associated to InterPro entries (e.g. mappings of entries to KEGG, Reactome, etc.) are incorrect.

We are currently working to fix this problem and re-release the data as soon as possible.  Note that this potentially affects the data in both the InterPro website and InterProScan XML files.

We apologise for the inconvenience and will make a new announcement once the problem is fixed and the new data is available (it will be called InterPro v43.1)

Please let us know if you have any questions about the above by using our support channels.