Closed richgain closed 7 years ago
Hi Richgain, thanks for spotting this issue. As far as I'm aware this is the first time that anyone has tried the RF2 -> RF1 conversion with the US Edition. It was developed to target just the International and Spanish editions. So while it does have some support for extensions, we've not really developed it in that direction. Apologies for not making that limitation explicit in the Readme file.
I'll put some time in to this early next week and hopefully get something working for you.
Best Wishes,
Peter
Thanks Peter. Sadly, the US seem to be taking the RF2 deadline as a hard stop. No RF1 version this release and no mention of the converter on the NLM site either.
Hi Peter Any luck with fixing the conversion tool for US extension files? Thanks, Richard
Hi Richard. Yes! Making the conversion tool recognise the US edition was a quick job, I just needed to add the module id. However, testing uncovered some data issues with the US Edition (some known, some news to us) which I needed to write some workarounds/cleanup for. The code is now working through to completion, but really I want to compare a conversion of March 2016 done using to the tool against what the NLM themselves released and also a regression test to ensure I haven't impacted the International Edition. I can either check the code in now, or once testing is complete - whatever you prefer?
Hi That sounds positive. Would you mind checking the code in now so I can start experimenting with the output? I will certainly await the outcome of your testing before building our new release though. Thanks, Richard
On 4 April 2017 at 18:43, Peter G. Williams notifications@github.com wrote:
Hi Richard. Yes! Making the conversion tool recognise the US edition was a quick job, I just needed to add the module id. However, testing uncovered some data issues with the US Edition (some known, some news to us) which I needed to write some workarounds/cleanup for. The code is now working through to completion, but really I want to compare a conversion of March 2016 done using to the tool against what the NLM themselves released and also a regression test to ensure I haven't impacted the International Edition. I can either check the code in now, or once testing is complete - whatever you prefer?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/IHTSDO/rf2-to-rf1-conversion/issues/1#issuecomment-291577276, or mute the thread https://github.com/notifications/unsubscribe-auth/ABX7NlYVEE6BNbMao80SIKiDomRHQKb2ks5rsoE2gaJpZM4MllF3 .
Done! Please ensure that you're working from the develop branch. Obviously I don't want to merge into master before the testing is complete. Can I ask, out of interest, who you're creating this package for, Richard? Feel free to email me directly for privacy. pwi at snomed . org
I used the following command to process the US Edition:
java -jar -Xmx8g target/RF2toRF1Converter.jar ~/tmp/us_edition/SnomedCT_USEditionRF2_Production_20170301T120000.zip -v -u /Volumes/ram_disk
If you've got the memory to support it, a Ram Disk does speed up the initial stages.
hi. I tried to run the conversion program against the bundle that only consist of snapshot. And it failed. Any plan to release version that support snapshot?
Hi Rakhmat - as discussed, no current plans. You're the first person to mention it! Feel free to create a new issue to request this feature. Issue #1 should have been marked as closed.
I get the following output:
Consequently, I am currently unable to create an RF1 version of the US version of SNOMED.