Open GemmaTuron opened 3 months ago
can you assign me this issue @DhanshreeA ?, I would be happy to learn and work on it
Hello @Adhivp
If you are working on the Outreachy contribution period please follow the guidelines and the tasks set out on the specific issue, we are a small community and cannot provide support outside those. Thanks for your understanding
It's ok , hope to see support in the future, Have a nice day
I am pretty sure there was an issue for that but I cannot find it now. The catalog used to provide a nice table with the Eos Identifier, Slug and model name, whereas now I only see something like:
[
{
"Identifier": "eos9taz"
},
{
"Identifier": "eos8bhe"
}
]
Can we go back to having the nice table?
The command I am running is
ersilia catalog --local
Also:
catalog --local --more
gives:
[
{
"Identifier": "eos6tg8",
"Slug": "natural-product-fingerprint",
"Title": "Natural product fingerprint"
},
{
"Identifier": "eos43at",
"Slug": "molgrad-herg",
"Title": "Coloring molecules for hERG blockade"
},
{
"Identifier": "eos9ei3",
"Slug": "sa-score",
"Title": "Synthetic accessibility score"
},
{
"Identifier": "eos4zfy",
"Slug": "maip-malaria",
"Title": "MAIP: antimalarial activity prediction"
}
]
We could have something more informative, like whether the model is from docker or not
Hey @dzumii and @Malikbadmus this issue is also an interesting one with potential for increased exposure to the Ersilia CLI. Let me know if either of you wants to take this up after your tracking tasks and before we jump into writing unit tests. :)
We have two tasks here:
ersilia catalog --local
work when no models are available locally. This can return an empty list or better yet, a helpful message such as "No models present on the system. Run ersilia fetch [model id]
to fetch a model." Addressed in #1175 ersilia catalog --local --more
verbose in its output including information about how the model was fetched. Addressed here: https://github.com/ersilia-os/ersilia/pull/1173I think you can both work on one of these tasks. LMK what you think!
Yeah, interesting. I'll get started with the first task once we conclude the tracking functionality changes
I'll start working on the second task.
I am pretty sure there was an issue for that but I cannot find it now. The catalog used to provide a nice table with the Eos Identifier, Slug and model name, whereas now I only see something like:
[ { "Identifier": "eos9taz" }, { "Identifier": "eos8bhe" } ]
Can we go back to having the nice table? The command I am running is
ersilia catalog --local
@DhanshreeA , the table format previously used to display model information when you run the catalog
command was removed in the last commit, which can be found here, should we restore the table format or improve the current format by adding the additional information we are working on to the current dictionary output?
I am pretty sure there was an issue for that but I cannot find it now. The catalog used to provide a nice table with the Eos Identifier, Slug and model name, whereas now I only see something like:
[ { "Identifier": "eos9taz" }, { "Identifier": "eos8bhe" } ]
Can we go back to having the nice table? The command I am running is
ersilia catalog --local
@DhanshreeA , the table format previously used to display model information when you run the
catalog
command was removed in the last commit, which can be found here, should we restore the table format or improve the current format by adding the additional information we are working on to the current dictionary output?
Thanks @Malikbadmus this is useful.
@miquelduranfrigola requesting you to weigh in here - is there a particular reason why the use of tabulate
library was removed from printing local model catalog? I see that a lot of work was done in a related issue a while back but it was removed in the commit referenced by Malik here as part of cleaning up catalog.
Is your feature request related to a problem? Please describe.
When you try to run
ersilia catalog --local
but no models are available locally, instead of telling you this it outputs an error:Describe the solution you'd like.
We could add a better info - Not prioritary at all though
Describe alternatives you've considered
No response
Additional context.
No response