Chang.Liu

We can't solve this kind of errors. Docker is running in root mode, but for some security reasons, instead of using the root user, we create a normal user and...

Thank you for your comment. Indeed, after upgrading to the new version that expanded xenonpy to cover organic compounds (using RDKit), we start to consider separating installation of xenonpy based...

@ISkWW-Z3 Hi, thank you for your feedback. Our server found some technical issues from last week. We are trying to fix these, but the schedule still open. We hope everything...

@ISkWW-Z3 We are working on it. Technically everything is ready, but our server is running behind our institute's network. We have to reapply for public access permission from the system...

@YIshiyama8 Sorry for the inconvenience, our server will keep off-line for about two weeks. We are trying to fix the technical problem and bring some critical improvement.

Hi @okikosuke, we are moving on to provide the new MDL system for all users. Here, we prepared some scripts to access our under-developing MDL service, but please keep in...

@yyamaguchi Hi! MDL services are renewing to match more complicated searching cases. You can try to use the temporary scripts described [here](https://github.com/yoshida-lab/XenonPy/issues/210#issuecomment-836395641) to access our developing server for a review....

@deepakorani Could you please give us your error messages? We did some tests on our machines (macOS and Ubuntu) and found it works well. BTW, you have to use the...

@TsumiNa Thanks! This error seems from getting an empty return from the server. I will try to reproduce the error on my machine and check what happened.

@chotoQ After you followed the installation guides, it should give you a clean environment to run xenonpy. It seems someone else also got this error code. If you are using...