OHDSI Home | Forums | Wiki | Github

Atlas - Unable to view characterisation results


(Selva) #1

Hello Everyone,

We are trying to run a cohort characterization analysis. Though the execution is successful, when we try to view the results, it keeps loading forever. This is similar to this post but a different error message

Upon pressing CTRL+SHIFT+I, shows the below

@vineet_jain - Apologies I just saw your post. I also experience something similar. Have you found a solution to this?

(Chris Knoll) #2

I can’t tell, but there does seem to be a problem with the concept name when it is embedded into the HTML as a tooltip. Can you identify the full concept name or concept ID that has the title that looks like ALLEVYN DRESSING 4?

(Selva) #3

Hi @Chris_Knoll,

I am not sure whether i understood you correctly. Are you askibg me for concepts which are similar to Allevyn dressing?

This is what I found in Athena. Not sure whether it helps


(Chris Knoll) #4

I mean something in the concept name is causing some HTML error. Do you see the part in your screenshot where it says ‘invalid token’? And then it shows the value of the toltip binding…something in the HTML is malformed. You could use the chrome DOM inspector to see what the actual HTML element is.

But, looking at your search results, it looks like there are concept names with quotes in them., so looksl ike the problem could be the " in things like" ALLEVYN DRESSING 4"X4".

(Chris Knoll) #5

Looks like the fix for this was applied to the 2.8 branch, but possibly not applied back to a hotfix branch: https://github.com/OHDSI/Atlas/pull/2058/files. You can either wait for the 2.8 release to fix this, or the hotfix maintainers can look into making a hotfix release for this.

(Selva) #6

Thanks for your response @Chris_Knoll . Unfortunately am not a developer/don’t have expertise with javascript, Html, etc, so can I seek your help with the below?

  1. When you mean “hotfix maintainers”, should I reach out to anyone in the OHDSI community or should I find help from someone at our side who can address/resolve this specific issue? Should we just make changes to our Atlas prevalencestatconverter.js, conceptset.js and commonutil.js files as shown in this link and restart our ATLAS/WebAPI etc?

  2. from a non developer perspective, do you think just removing the double quotes from my concept names can also help in fixing the issue?

Unable to register descendant concepts in Atlas
(Chris Knoll) #7

If you can make those small edits in the Atlas javascript files, then that’s the simplest approach. You won’t need to restart WebAPI, just refresh your browser. I don’t recommend making any edits to the vocabulary.

(Selva) #8

Fantastic. Thanks @Chris_Knoll

(mintmountain89) #9


We are facing similar issues in viewing both characterisation and cohort pathway results. While the execution is successful, the counts returned are ‘0’, as shown below:

However, when running a separate query via sql it shows that there is a set of people who fulfil the criteria for the cohorts in the analysis.

Upon pressing CTRL+SHIFT+I, the error message given is as follows:

(Sreemanee) #10

Hi @Chris_Knoll,

I work with Hui Xing who has a follow up question on this topic. We would be most grateful if you had some advice for us with regards to the errors we are seeing please.

Thank you very much!

Best wishes,

(Chris Knoll) #11

I’m sorry, but I can’t tell from your errors. I know this is unrelated, but why are you getting a 500 response when going to: /WebAPI/notifications?

(mintmountain89) #12

Thanks @Chris_Knoll for the reply

I’m not too sure about the 500 Error response, however, it seems to appear no matter which page of our local Atlas we open, and is always referring to this webpage: http://localhost:8080/WebAPI/notifications

Typical error messages we encounter when opening an atlas webpage (or clicking refresh):


If we type http://localhost:8080/WebAPI/notifications into the url bar, this is what we see:

Currently the version that we’ve installed is Atlas v2.7.0 and webapi 2.7.0 - could this be something in previous versions of Atlas and will it help if we installed a later version? Sorry that we are not too sure how to debug or interpret the message as we do not have experience with http.

Going back to the characterisation and cohort pathways result, one thing is that while the cohort definitions tables are populated after running the execution, the concept sets are empty. Is this expected?

Cohort Definitions (cohorts are there)

Concept Sets (concept sets are absent)

Previously we also had issues creating concept sets which we are still not able to resolve (see here), so I am not too sure if this could be related and it might help in the debugging of this issue. Any ideas?

Thanks again!

Best Regards,
Hui Xing

(Konstantin Yaroshovets) #13

I recommend to share here stack trace for error from Tomcat logs. It’s not clear what happens. But the problem happens on WebAPI side.

(mintmountain89) #14

Thank you, @Konstantin_Yaroshove.

Could you advise how we could get the stack trace for error from Tomcat logs? I found a couple of files on Tomcat 9.0/logs folder.

Thanks :slight_smile:

Best regards,
Hui Xing

(mintmountain89) #15

Hi all,

Just to update that we had resolved this issue by first fixing another issue with the concept sets mentioned in this post. :slight_smile:

Thanks for the help!

Hui Xing