Bioinformatics.org
[University of Birmingham]
[Patsnap]
Not logged in
  • Log in
    		•

    Bioinformatics.org
    Membership (44456+) Group hosting [?] Wiki
    Franklin Award
    Sponsorships

    Careers
    About bioinformatics
    Bioinformatics jobs

    Research
    All information groups
    Online databases Online analysis tools Online education tools More tools

    Development
    All software groups
    FTP repository
    SVN & CVS repositories [?]
    Mailing lists

    Forums
    News & Commentary
  • Submit
  • Archives
  • Subscribe

    • Jobs Forum
    (Career Center)
  • Submit
  • Archives
  • Subscribe
    		•

    RDFScape: Semantic Web and data analysis - Support tickets

    Submit | Open tickets | Closed tickets

    [ Ticket #256 ] Incosistencies after reloading
    Date:
    04/01/06 09:33
    Submitted by:
    sergentpepper     		Assigned to:
    sergentpepper
    Category:
    Internals     		Priority:
    4
    Ticket group:
    Bug - marginal     		Resolution:
    Unset
    Summary:
    Incosistencies after reloading
    Original submission:
    After activating a new context and reloading ontologies, several things seem to be inconsistent. Same effect "may" be there when just reloading ontologies.
    Please log in to add comments and receive followups via email.
    Followups
    Comment Date By
    To verifies (not experienced) 01/24/08 19:51 sergentpepper
    When reloading the the set of ontologies, for instance after changing analysis context, some data structyre seems to remain dirty provoking several errors.
    A temporary workaround is to restart RDFScape each time a new analysis context is used (if these problems are encuntered)     		07/31/07 04:26 sergentpepper
    Yes... init() and update() method have to be checked and cleaned.
    Possibly at the end we should have:
    init() initialization
    reset() often just calling init(), but we may want something to be in memory
    touch()/update() just one method.
    To check waht we want after a context initialization.
    Plus a set of specialized methods like:
    updateAfterNamespaceChange()
    updateAfterKnowledgeBaseChange()
    Should we remove these and just use update() ?
    Also, memory clear/reset right now is incomplete..
    		04/01/06 09:50 sergentpepper

    1 - 2 of 2

    Dependent on ticket
    "Save context" should be improved
    Reasoning inconsistency
       
    No results for "Dependent on Task"
    No other tickets are dependent on this ticket
    Ticket change history
    Field Old value Date By
    status_id Open 04/21/08 12:49 sergentpepper
    close_date 12/31/69 19:00 04/21/08 12:49 sergentpepper
    status_id Unset 07/31/07 04:26 sergentpepper
    category_id Unset 07/31/07 04:26 sergentpepper
    priority 5 04/01/06 09:50 sergentpepper
    assigned_to unset 04/01/06 09:50 sergentpepper
    bug_group_id Unset 04/01/06 09:50 sergentpepper

     
    Copyright © 2024 Scilico, LLC · Privacy Policy