Closed Nathalie06 closed 3 years ago
@Nathalie06 It looks like your project database is corrupted for some reason There is no limit to the number of simulation you can save in a project
Was your project saved on a network drive or locally?
Do you have a backup of your project?
if you can share your project, can you add it to this issue? If not, you can send it to me and I can take a look and see if we can save some of the content (michael@design2code.ca)
I saved my project on a network drive. Yes I had a backup of my project so I was able to rebuild this model. When I tried to simulate a population, I didn't have access to the same parameters as individual simulation. Individual simulation (parameters/distribution/partition coefficient): Population simulation (parameters/distribution/partition coefficient):
I want to change B/P ratio to 1 instead of the calculated value but I can't in population simulation. Moreover, some parameters are different from the individual simulation (Ka (acidic phospholipids) and Partition coefficient (blood cells/plasma unbound) with same compounds ? Is it a bug ?
Thanks for your answers Best, Nathalie
I solved my first issue but I still have the question concerning individuals and population:
Thanks in advance for an explanation, Best, Nathalie
@Nathalie06 If you have questions, your best bet is to post in the forum so that community experts can answer. PKSim issues are for bug reports only. I moved your issue yesterday to the forum. Let's follow up there
Hello,
I am a new PKsim's user and when I tried to save my first and successful PBPK model, I have an error message, I copied this message below. I have 8 individual simulations and 2 population simulations. Is there a limit of size ?
Can you help me ? Best, Nathalie
Application: PK-Sim® 8.0.22
could not load an entity: [OSPSuite.Infrastructure.Serialization.ORM.MetaData.MetaDataContent#147][SQL: SELECT metadataco0_.Id as id1_180, metadataco0_.Data as data2_180 FROM CONTENTS metadataco0 WHERE metadataco0.Id=?]
database disk image is malformed database disk image is malformed
Stack trace: