From: Pablo C. <pc...@cn...> - 2019-12-05 07:42:01
|
We are also planning to organize a course for developers this summer. Keep tunned. On 4/12/19 19:52, Pablo Conesa wrote: > > Dear Ian, > > I guess you've already found the developers page > <https://scipion-em.github.io/docs/docs/developer/developers.html>, > there are lots of info but also work to be done. But recently we > updated it. > > > More precisely answering your questions: > > > Scipion has it's own model where Em "concepts" are reflected. > Micrograph is here > -->https://github.com/I2PC/scipion/blob/master/pyworkflow/em/data.py#L642 > > They are pointers, all the binary files remain in the file system > and only the paths to them are kept in the sqlites files. > > Usually the protocol you implement needs to take that into > consideration, see an example here: > https://github.com/scipion-em/scipion-em-sphire/blob/master/sphire/protocols/protocol_cryolo_picking.py#L188 > > > But many of the protocols have somehow a "possible" conversion step. > > > We run a slack workspace for developers and facility managers to have > more direct conversations. I can add you if you want. > > > Keep asking your doubts, we are here to help you. > > > All the best, Pablo > > > > On 4/12/19 16:26, Ian Liu Rodrigues wrote: >> Dear Scipion community, >> >> I'm Ian Liu Rodrigues, working with software development at the >> National Laboratory of Nanotechnology, Brazil. I'm trying to >> understand how the plugin architecture works so I can make my own >> plugins. Here are my questions: >> >> * How is a micrograph represented inside Scipion? >> * Is the image *imported* into the database or just pointers to >> external files? >> * How does Scipion knows when to convert an input to a program? >> >> I'm very new to this, so sorry if I'm asking anything basic 😉 >> >> Kind regards, >> >> 👨💻 Ian L. Rodrigues >> 🏢 CNPEM, LNNano, CME >> 📞 +55 19 3512 1144 >> >> >> Aviso Legal: Esta mensagem e seus anexos podem conter informações >> confidenciais e/ou de uso restrito. Observe atentamente seu conteúdo >> e considere eventual consulta ao remetente antes de copiá-la, >> divulgá-la ou distribuí-la. Se você recebeu esta mensagem por engano, >> por favor avise o remetente e apague-a imediatamente. >> >> Disclaimer: This email and its attachments may contain confidential >> and/or privileged information. Observe its content carefully and >> consider possible querying to the sender before copying, disclosing >> or distributing it. If you have received this email by mistake, >> please notify the sender and delete it immediately. >> >> >> >> _______________________________________________ >> scipion-users mailing list >> sci...@li... >> https://lists.sourceforge.net/lists/listinfo/scipion-users > -- > Pablo Conesa - *Madrid Scipion <http://scipion.i2pc.es> team* > > > _______________________________________________ > scipion-users mailing list > sci...@li... > https://lists.sourceforge.net/lists/listinfo/scipion-users -- Pablo Conesa - *Madrid Scipion <http://scipion.i2pc.es> team* |