New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Code error for new Validation usecase #269
Comments
@alex4200 : I am not sure of the origin of this error, and have the feeling this is a Collab environment issue. I have once in the past got this error when testing through a different account. But in all others it works. Could you try using a different account? And maybe ask someone from the Collab team on the cause, and how to avoid it? p.s. Note: This is a two-phase validation test.... only the first phase is currently implemented in the Jupyter notebook (The second part titled "2. ===== Soft Constraints Validation =====" will be added soon after testing). I wanted to have the UseCase structure in place for testing. |
@appukuttan-shailesh : Even with a different user I get the same error. And a google search does not bring a single hit. I am using tornado version 4.5.3. Maybe there is a mismatch in the version you are using. Here is the full pip-freeze list:
Otherwise I suggest to create a ticket on the 'tornado' github page. |
This is happening within the |
Temporarily, you could do the following for testing:
I am not sure if this should be checked inside the usecase. It is quite generic and probably needs to be resolved by the Collaboratory team across all environments. |
p.s. note that your pip freeze states:
|
@appukuttan-shailesh Thanks for noticing that. I just did a |
I have created a ticket for this on the forum: |
The correct version of tornado to be used is 4.5.3. |
@appukuttan-shailesh : I have found the part that seems to update I have run the use case
|
@alex4200 : I am a bit surprised that it has popped-up there. Because I have previously encountered the same issue in other modules not using |
@appukuttan-shailesh : I just retested that use case "Basal Ganglia Morphology Validation" from scratch, i.e. with the user
You can ask fabrice.gaillard@epfl.ch to reset your container. He needs your |
@alex4200 : I realize why this has come up. I think that it might be better for you to test the usecase once the second part (by @pedroernesto) is added. I shall update you of the same. Apologies for the mix-up. |
@alex4200 : error corrected, however you will have new updates soon from our side before the usecase is completed and ready to use |
Regarding the initial error involving 'tornado', I found that it was related to this issue: I have now resolved this by changing @alex4200 : Shall let you know when the usecase is ready. |
My suggestion is to use: |
@jdcourcol : currently I was doing |
@alex4200 : the usecase is ready at: https://collab.humanbrainproject.eu/#/collab/8123/nav/78914 A second part (soft-constraints check) has been added to test some morphological features in FS inter-neurons. The other cell types considered in the first part of the test (hard-constraints check), i.e. D1- and D2- MSNs, may also be tested as soon as more experimental data is available. Just one feature can be time-consuming when testing "big" cells: the field's diameter for axon and basal dendrite. So, for a quick check, better to use small SWC files (<1Mb) amongst the ones listed in the first part of the test. For instance: 10 - C170897A-I1-rep-cor.swc |
@pedroernesto : In the cell in Part I I get the following error. It seems the package 'tabulate' is missing...
|
@alex4200 : resolved now. p.s. Is there an easy way to reset Jupyter container (without having to contact Collab support)? Just to be able to do on a more frequent basis as and when needed. |
@appukuttan-shailesh : Seems to work now. And no, there is no easy way (yet) to reset one's container. This might be a feature of an updated collaboratory (after SGA1)... |
Code error in second cell (DEV environment):
The text was updated successfully, but these errors were encountered: