Ok, I found the solution to this problem.
If someone wants to know it... the exception is thrown because the path of the project repository pointed to a folder that didn't exist.
-
Problems with LifeScope
Hi! Mi name is Alfonso, I'm from Spain, and this is my first message in this forum. I've been visiting it for a few months, and I've registered because I've got a problem with LifeScope, anyway I'll try to help as much as I can in other threads.
As I said, I have a problem with LifeScope. I've opened the shell with lscope.sh shell -u user -w passwd, but I can't create a project (cd projects and mk ecoli). The program tells me "Server returned error status: 500, message: Error saving project" after trying to execute the cmd mk.
In the file server.log I can read the response "19 mar 2013 12:06:40,214 ERROR [Grizzly-9998-WorkerThread(4)] ProjectManager:99 - Error writing .project file
java.io.FileNotFoundException: /data/results/projects/lifescope/ecoli/.project.ctmp (No such file or directory)..."
The file server.err: "19-mar-2013 12:06:40 com.sun.jersey.spi.container.ContainerResponse traceException
GRAVE: Mapped exception to response: 500 (Internal Server Error)
com.lifetechnologies.bioscope.webservice.ServerException at com.lifetechnologies.bioscope.webservice.ProjectManager.saveProject(ProjectManager.java:100)
at com.lifetechnologies.bioscope.webservice.ProjectManager.createProject(ProjectManager.java:63)..."
Does anyone know what should I do to execute those commands??
Thank you very much.
-
Love this - good data definitely starts from good input, and poor input can only give relatively poor data. I particularly like the mention of Nanodrop/absorbance based methods for quantification. It's such a toss up if you'll get an accurate reading or what amounts to a randomly generated number, and a lot of library/sequencing related issues can be traced back to poor quant.Yesterday, 11:43 AM
-
I’m not a sequencing expert. I’m a purification scientist who uses NGS to evaluate workflows my group develops. With this perspective, we think about the sample first and the NGS workflow second. The sequencer is an exceptionally honest reporter, but it can only report on what you give it, so whether you get clean, interpretable data from an NGS workflow is largely determined before you begin.
Here are nine questions we think about, in roughly the order they matter, before...
Leave a comment: