← Back to team overview

kaliveda-dev team mailing list archive

[Bug 1131725] Re: KaliVeda ne s'ouvre pas

 

il fallait être un peu patient
comme il était indiqué à la fin des messages:

Info in <KVDataSetManager::Init>: Using available dataset cache file: MaxCacheTime = 86400 seconds
Info in <KVDataSetManager::CheckCacheStatus>: Cached file is 249696 seconds old

, la version "cachée" de la liste des datasets disponibles était périmée (on la garde pendant
24 heures = 86400 secondes), donc Mr. KaliVeda était parti intérroger irods pour savoir
quelles données sont disponibles.
ça prend un peu de temps (30 secondes maximum)
je viens de le faire, ça doit démarrer rapidement maintenant

-- 
You received this bug notification because you are a member of KaliVeda
Development Team, which is subscribed to KaliVeda.
https://bugs.launchpad.net/bugs/1131725

Title:
  KaliVeda ne s'ouvre pas

Status in KaliVeda data analysis framework:
  New

Bug description:
  Depuis mercredi 20 Février après-midi, je n'arrive plus à ouvrir
  KaliVeda. J'obtiens le message suivant :

  [legouee@ccage032 legouee]$ 
  [legouee@ccage032 legouee]$ KaliVedaGUI &
  [3] 26732
  [legouee@ccage032 legouee]$ Info in <KVBase::InitEnvironment>: Initialising KaliVeda environment...
  Info in <KVBase::InitEnvironment>: Using KaliVeda version 1.8.9 built on 2013-02-13
  Info in <KVBase::InitEnvironment>: (BZR branch : bzr+ssh://bazaar.launchpad.net/%2Bbranch/kaliveda/ revision#790 (clean=0) date : 2013-02-13 11:56:07 +0100)
  Info in <KVLifeTimeTable::Initialize>: lifetime_nudat2.data will be read
  Info in <KVLifeTimeTable::Initialize>: Set up map for 2829 nuclei
  Info in <KVLifeTimeTable::Initialize>: table initialised correctly for 2829 nuclei
  Info in <KVChargeRadiusTable::Initialize>: chargeradii_angeli.data will be read
  Info in <KVChargeRadiusTable::Initialize>: Set up map for 909 nuclei
  Info in <KVChargeRadiusTable::Initialize>: table initialised correctly for 909 nuclei
  Info in <KVMassExcessTable::Initialize>: massexcess_nudat2.data will be read
  Info in <KVMassExcessTable::Initialize>: Set up map for 3104 nuclei
  Info in <KVMassExcessTable::Initialize>: table initialised correctly for 3104/3104 nuclei
  Info in <KVAbundanceTable::Initialize>: abundance_nudat2.data will be read
  Info in <KVAbundanceTable::Initialize>: Set up map for 285 nuclei
  Info in <KVAbundanceTable::Initialize>: table initialised correctly for 285/285 nuclei
  Info in <KVElementDensityTable::Initialize>: element_densities.data will be read
  Info in <KVElementDensityTable::Initialize>: Set up map for 97 nuclei
  Info in <KVElementDensityTable::Initialize>: table initialised correctly for 97/97 nuclei
  --------
  Info in <KVNDTManager::Print>: 5 Available nuclear data tables
  name=LifeTime file=lifetime_nudat2.data number of nuclei stored=2829
  name=ChargeRadius file=chargeradii_angeli.data number of nuclei stored=909
  name=MassExcess file=massexcess_nudat2.data number of nuclei stored=3104
  name=Abundance file=abundance_nudat2.data number of nuclei stored=285
  name=ElementDensity file=element_densities.data number of nuclei stored=97
  --------
  Info in <KVDataSetManager::Init>: Using available dataset cache file: MaxCacheTime = 86400 seconds
  Info in <KVDataSetManager::CheckCacheStatus>: Cached file is 249696 seconds old

  [3]  + Suspended (tty output)        KaliVedaGUI
  [legouee@ccage032 legouee]$ 

  
  Quelqu'un a-t-il déjà rencontré ce problème ?

  Merci d'avance.

  Elodie.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kaliveda/+bug/1131725/+subscriptions


References