[PyMOL] 3rd Call For Papers - 26th Annual Tcl/Tk Conference (Tcl'2019)
Hello pymol-users, fyi ... 26th Annual Tcl/Tk Conference (Tcl'2019) https://www.tcl-lang.org/community/tcl2019/ November 04 - 08, 2019 Crowne Plaza Houston River Oaks 2712 Southwest Freeway, 77098 Houston, Texas, USA [ NEWS * Our keynote speaker is [Will Duquette](https://github.com/wduquette) talking about "Tcl, Rust, and the Death of Rube Goldberg" * [Submission is open](https://www.tcl-lang.org/community/tcl2019/cfp.html) It is 4 weeks to the deadline. * Registration is open. Please have a look at https://www.tcl-lang.org/community/tcl2019/register.html * The tutorials are known. See https://www.tcl-lang.org/community/tcl2019/tutorials.html ] Important Dates: Abstracts and proposals due September 09, 2019 Notification to authors September 16, 2019 WIP and BOF reservations open August 12, 2019 ** may change ** Registration opensSeptember 09, 2019 ** open already ** Author materials due October 14, 2019 Tutorials Start November 04, 2019 Conference starts November 06, 2019 Email Contact:tclconfere...@googlegroups.com Submission of Summaries Tcl/Tk 2019 will be held in Houston, Texas, USA from November 04, 2019 to November 08, 2019. The program committee is asking for papers and presentation proposals from anyone using or developing with Tcl/Tk (and extensions). Past conferences (Proceedings: https://www.tcl-lang.org/community/conferences.html) have seen submissions covering a wide variety of topics including: * Scientific and engineering applications * Industrial controls * Distributed applications and Network Managment * Object oriented extensions to Tcl/Tk * New widgets for Tk * Simulation and application steering with Tcl/Tk * Tcl/Tk-centric operating environments * Tcl/Tk on small and embedded devices * Medical applications and visualization * Use of different programming paradigms in Tcl/Tk and proposals for new directions. * New areas of exploration for the Tcl/Tk language Submissions should consist of an abstract of about 100 words and a summary of not more than two pages, and should be sent as plain text to tclconfere...@googlegroups.com no later than September 09, 2019. Authors of accepted abstracts will have until October 14, 2019 to submit their final paper for the inclusion in the conference proceedings. The proceedings will be made available on digital media, so extra materials such as presentation slides, code examples, code for extensions etc. are encouraged. Printed proceedings will be produced as an on-demand book at lulu.com Online proceedings will appear via https://www.tcl-lang.org/community/conferences.html The authors will have 30 minutes to present their paper at the conference. The program committee will review and evaluate papers according to the following criteria: * Quantity and quality of novel content * Relevance and interest to the Tcl/Tk community * Suitability of content for presentation at the conference Proposals may report on commercial or non-commercial systems, but those with only blatant marketing content will not be accepted. Application and experience papers need to strike a balance between background on the application domain and the relevance of Tcl/Tk to the application. Application and experience papers should clearly explain how the application or experience illustrates a novel use of Tcl/Tk, and what lessons the Tcl/Tk community can derive from the application or experience to apply to their own development efforts. Papers accompanied by non-disclosure agreements will be returned to the author(s) unread. All submissions are held in the highest confidentiality prior to publication in the Proceedings, both as a matter of policy and in accord with the U. S. Copyright Act of 1976. The primary author for each accepted paper will receive registration to the Technical Sessions portion of the conference at a reduced rate. Other Forms of Participation The program committee also welcomes proposals for panel discussions of up to 90 minutes. Proposals should include a list of confirmed panelists, a title and format, and a panel description with position statements from each panelist. Panels should have no more than four speakers, including the panel moderator, and should allow time for substantial interaction with attendees. Panels are not presentations of related research papers. Slots for Works-in-Progress (WIP) presentations and Birds-of-a-Feather sessions (BOFs) are available on a first-come, first-served basis starting in August 12, 2019. Specific instructions for reserving WIP and BOF time slots will be provided in the registration information available in August 12, 2019. Some WIP and BOF time slots will be held open for on-site reservation. All attendees with an interesting work in progress should consider reserving a WIP slot. Registration Information More information on the conference is available the conference Web
Re: [PyMOL] Label volume
And how to place a single arbitrary label on the object or segment? Em seg, 12 de ago de 2019 às 13:55, Pedro Lacerda escreveu: > Hi PyMOL list, > > Is possible toshow a label independent of the associated object be > enabled? > > Or is possible to label a volume or map? > -- > Pedro Sousa Lacerda > > > *Laboratório de Bioinformática e Modelagem Molecular* > *Faculdade de Farmácia / UFBA* > > *@pslacerda* > > *+55 71 9 9981-1856* > -- Pedro Sousa Lacerda *Laboratório de Bioinformática e Modelagem Molecular* *Faculdade de Farmácia / UFBA* *@pslacerda* *+55 71 9 9981-1856* ___ PyMOL-users mailing list Archives: http://www.mail-archive.com/pymol-users@lists.sourceforge.net Unsubscribe: https://sourceforge.net/projects/pymol/lists/pymol-users/unsubscribe
[PyMOL] Label volume
Hi PyMOL list, Is possible toshow a label independent of the associated object be enabled? Or is possible to label a volume or map? -- Pedro Sousa Lacerda *Laboratório de Bioinformática e Modelagem Molecular* *Faculdade de Farmácia / UFBA* *@pslacerda* *+55 71 9 9981-1856* ___ PyMOL-users mailing list Archives: http://www.mail-archive.com/pymol-users@lists.sourceforge.net Unsubscribe: https://sourceforge.net/projects/pymol/lists/pymol-users/unsubscribe
Re: [PyMOL] count_atoms and states
Thanks for the info. I also didn't realize that states started at 1. Maybe the nonexistent state warning is something that should be implemented elsewhere as well. As for the implicit *or*, you can find it in https://pymolwiki.org/index.php/Selection_Algebra#Selection_Operator/Modifier_Table under the *Logical* section. I agree that it can be easy to miss—good thing you caught this behavior in your code. Have a great day, Cole On Fri, Aug 9, 2019 at 6:34 PM Pedro Lacerda wrote: > So missing boolean operators are filled with OR, for me this is should be > a big and loud WARNING. I almost messed everything up because it almost > passed in my tests. > > Also I mistake states a couple of days on multi-model files because I was > counting from ZERO but states starts on ONE. That was until I needed > get_area, it properly stated that my states were nonexistant. > > So these were my personal thoughts and issues about. > > Have a nice weekend! > > Em sex, 9 de ago de 2019 12:41, Pedro Lacerda > escreveu: > >> Question answered. >> >> Best regards! >> >> Em sex, 9 de ago de 2019 às 12:33, Christian "Cole" French < >> christian.fre...@schrodinger.com> escreveu: >> >>> Hi Pedro, >>> >>> *count_states* is correct here; there's only 1 state, which is state 1. >>> The reason for the observed *count_atoms* behavior is that "polymer" >>> and "state" are different operators in the selection algebra, so putting >>> them together without a logical operator such as "and" or "or" between them >>> indicates an implicit "or". So you're actually counting atoms which match >>> "polymer" *or* "state X", which is why the number only goes up to 8627 >>> when you count state 1. >>> >>> This might clear up your scope question as well, but please indicate if >>> otherwise. >>> >>> Best, >>> Cole >>> >>> On Fri, Aug 9, 2019 at 10:55 AM Pedro Lacerda >>> wrote: >>> I'm also puzzled by the scope of state: *PyMOL>count_atoms polymer state 1 within 5 of resn NAP* > count_atoms: 8205 atoms > > *PyMOL>count_atoms polymer state 1 within 0 of resn NAP* > count_atoms: 8109 atoms > > *PyMOL>count_atoms polymer (state 1) within 0 of resn NAP* > count_atoms: 8109 atoms > > *PyMOL>count_atoms (polymer (state 1)) within 0 of resn NAP* > count_atoms: 192 atoms > > *PyMOL>count_atoms (polymer (state 0)) within 0 of resn NAP* > count_atoms: 0 atoms > Em sex, 9 de ago de 2019 às 11:31, Pedro Lacerda escreveu: > Hi, > > There is only one state but the atom counting changes between states > 0, 1 and 2. > > > What this means? > > *PyMOL>fetch 1e92* >> >> TITLE Pteridine reductase 1 from Leishmania major complexed with >> NADP+ and dihydrobiopterin >> ExecutiveLoad-Detail: Detected mmCIF >> CmdLoad: loaded as "1e92". >> >> *PyMOL>count_atoms polymer state 0* >> count_atoms: 7917 atoms >> >> *PyMOL>count_atoms polymer state 1* >> count_atoms: 8627 atoms >> > *PyMOL>count_atoms polymer state 2* >> count_atoms: 7917 atoms >> > *PyMOL>count_states * >> cmd.count_states: 1 states. >> > > -- > Pedro Sousa Lacerda > > > *Laboratório de Bioinformática e Modelagem Molecular* > *Faculdade de Farmácia / UFBA* > > *@pslacerda* > > *+55 71 9 9981-1856* > -- Pedro Sousa Lacerda *Laboratório de Bioinformática e Modelagem Molecular* *Faculdade de Farmácia / UFBA* *@pslacerda* *+55 71 9 9981-1856* ___ PyMOL-users mailing list Archives: http://www.mail-archive.com/pymol-users@lists.sourceforge.net Unsubscribe: https://sourceforge.net/projects/pymol/lists/pymol-users/unsubscribe >>> >>> >> >> -- >> Pedro Sousa Lacerda >> >> >> *Laboratório de Bioinformática e Modelagem Molecular* >> *Faculdade de Farmácia / UFBA* >> >> *@pslacerda* >> >> *+55 71 9 9981-1856* >> > ___ > PyMOL-users mailing list > Archives: http://www.mail-archive.com/pymol-users@lists.sourceforge.net > Unsubscribe: > https://sourceforge.net/projects/pymol/lists/pymol-users/unsubscribe ___ PyMOL-users mailing list Archives: http://www.mail-archive.com/pymol-users@lists.sourceforge.net Unsubscribe: https://sourceforge.net/projects/pymol/lists/pymol-users/unsubscribe
