Re: [Beg-bogas] Bogas, not working properly .. again
apparently the problem only exists from spidermite .... after looking into it, it turns out that the genomic DB is not found anymore because it has changed names ??? it should be fixed now, but current session will not work so you'll have to refresh them. Also, please try not to blame the system for user-mishap. cheers, L. On 28/11/2011 12:28, Pierre Rouze wrote:
:o :-( :'(
What is going on this time ??? It is so often not working probably ... Can't we have a STABLE implementaion for once ?
Today : no way to open a spidermite entry (tetur03g08830)in either artemini or GenomeView (please correct parser manually !!! BEDParser)
Pierre, kind of real fed-up
-- ============================================================== Lieven Sterck, PhD Tel:+32 (0)9 3313821 Fax:+32 (0)9 3313809 VIB Department of Plant Systems Biology, UGent Bioinformatics and Evolutionary Genomics Division Technologiepark 927, B-9052 Gent, Belgium Email: lieven.sterck@psb.vib-ugent.be Website: http://bioinformatics.psb.ugent.be ============================================================== "Facts are meaningless. You could use facts to prove anything that's even remotely true" - H. Simpson
On 11/28/2011 11:32 AM, Lieven Sterck wrote:
apparently the problem only exists from spidermite .... after looking into it, it turns out that the genomic DB is not found anymore because it has changed names ???
Thanks for fixing it! Any idea who changed the genomic DB name? So we can attribute proper blame! These things should not happen, I guess we can all agree on that. So let's find out what went wrong, who made the mistake and make sure it never happens again. Either by putting technical limitations in place or by having Pierre have a little chat with the perpetrator ;-). cheers, Thomas
Wel that happens when you want to have the database names changed, because you do find the names "LATEST" vague and want it changed on the spot. Then It is not easy to make a change when the same configuration change needs to be made at several places. having a configuration at one and the same place would prevent this So I made the change, because Pierre didn't like the "LATEST" tag in the name. I made the changes in the yaml file that I knew would break, if there was an other place ... that needed fixing well then that one broke. Who to blame... The one who wanted the change, the one that made the change and/or the one that made it such that it can brake ... make your choice. cheers Stephane On 28 Nov 2011, at 18:07, Thomas Abeel wrote:
On 11/28/2011 11:32 AM, Lieven Sterck wrote:
apparently the problem only exists from spidermite .... after looking into it, it turns out that the genomic DB is not found anymore because it has changed names ???
Thanks for fixing it!
Any idea who changed the genomic DB name? So we can attribute proper blame! These things should not happen, I guess we can all agree on that. So let's find out what went wrong, who made the mistake and make sure it never happens again. Either by putting technical limitations in place or by having Pierre have a little chat with the perpetrator ;-).
cheers, Thomas
=================================================== Stephane Rombauts Principal Scientific staff Bioinformatics & Systems Biology Division of the Plant Systems Biology Department Tel:+32 (0)9 331 38 21 fax:+32 (0)9 3313809 VIB Department of Plant Systems Biology, Ghent University Technologiepark 927, 9052 Gent, BELGIUM strom@psb.vib-ugent.be http://bioinformatics.psb.ugent.be/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
On 28/11/2011 17:32, Lieven Sterck wrote:
apparently the problem only exists from spidermite .... after looking into it, it turns out that the genomic DB is not found anymore because it has changed names ???
it should be fixed now, but current session will not work so you'll have to refresh them.
Also, please try not to blame the system for user-mishap.
cheers, L.
I deliberately put myself at the position of a common user, first because it is what I am for most of it, and second because I use it so regularly that it is the most valuable feedback you can get as authors & developpers. And a normal user does NOT care where the problem comes from, and does not want to know about it in most cases. He simply want a tool to work properly, routinely, reliably. And if it is not working this way, he will abandon it, as simple as that. And I persist to say that BOGAS which is a very nice tool in its principle is also among the ones to have the worst score in term of reliablility. I have not the time to do it, but I should count the number of mails I sent where I was in trouble for one or another reason. With Tetranychus there is high chance that we will get a lot of new users: up to us to get them happy or not. This is the reason why I point to Stephane that these users want to have a clean Blast offer, which means knowing exactly what are the sequences they are blasting against... "latest" is meaningless, as it could be anything from yesterday, to a week ago or a month or a year or even several years ... No user would blame a server not showing the very late things, but he expects a reliable answer: So, the bottom line is, keep the tool up & going, working properly. And only make the changes on regular basis, after a complete reliability check. This is valid for every BOGAS which is public or open to a large user community. We can have trial versions of restricted access for many purposes otherwise.
On 28/11/2011 12:28, Pierre Rouze wrote:
:o :-( :'(
What is going on this time ??? It is so often not working probably ... Can't we have a STABLE implementaion for once ?
Today : no way to open a spidermite entry (tetur03g08830)in either artemini or GenomeView (please correct parser manually !!! BEDParser)
Pierre, kind of real fed-up
-- Pierre ROUZE Bioinformatics / Senior Expert Scientist VIB Department of Plant Systems Biology Ghent University Technologie park 927, B-9052 GENT BELGIUM Tel :32.933 13694 Cell.Phone : 32.476 638 304 Fax :32.933 13809 pierre.rouze@psb.vib-ugent.be http://www.psb.ugent.be/bioinformatics ¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨ prediction is very difficult, especially about the future Niels Bohr
participants (4)
-
Lieven Sterck -
Pierre Rouze -
Stephane Rombauts -
Thomas Abeel