[hugin-ptx] Re: Command line interface for hugin please
On 21 Nov., 22:41, john doe guerrerodelu...@gmail.com wrote: Iḿ really interested in both gawk and that ptsed tool you mentioned...didnt know about it.. What platform are you on? I have used awk/gawk a lot when I was still working as a programmer, so I can probably help if your efforts become more involved. awk is much more powerful than just changing a few words in a bit of text. Everyone who's into scripting would do well to learn at least a bit of it; many tasks that seem daunting otherwise become very easy indeed. Awk is really good at text processing, but that is also it's main scope. As a general purpose language it becomes a bit awkward. If you want a tool that can do everything awk does plus everything else you'd expect from a programming language, go for Python. You won't regret it. In Python you can also use regular expressions to pick out bits of text and then change them to something else; since it's general- purpose, it's more verbose but also much more flexible. ptsed is part of the Panotools-Script package: http://search.cpan.org/dist/Panotools-Script/ This is a collection of perl scripts to deal with pto files. It has a lot of good stuff in there, but the documentation is at times a bit scanty. For me, the problem is that the scripts are in perl (don't worry, you can just use them without knowing what language they're in) - and I can't - at least now - get myself to learn perl. They work just fine, though. thanks a bunch for the info..and your scripts are nice.. No big deal - I just tried to point you in the right direction, you can hardly call these snippets 'scripts'... As Jan Martin has pointed out above, there is a helpful introduction to panorama scripting in the panotools wiki: http://www.google.com/url?sa=Dq=http://wiki.panotools.org/Panorama_scripting_in_a_nutshell%23Simple_command-line_stitchingusg=AFQjCNFyQ7ku1BjMRkrsj8HgfUdRqei8og with regards Kay -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
Re: [hugin-ptx] Several questions about hugin sourcecode
I am not a programmer. And I have not looked at this code. But. Questions like this (which seem to appear fairly often) greatly concern me as a user. While I am not a programmer, I *am* familiar with certain conventions or best practices. One of those being something called COMMENTING YOUR CODE. I realize this project is an Open Source one, and all that but... Shouldn't questions like those below be addressed (at least at the first level) as comments in the code? Is it truly the case that when inspecting the code described that answers to these questions are mysteries?? eo On Nov 21, 2010, at 7:24 AM, Cugucas wrote: Hi，all I have met some questions while reading the sourcecode of hugin. 1. I noticed that there are two functions named createTransform and createInvTransform in PanoToolsInterface.cpp. What are they used for? In createTransform, there are two lines: m_srcTX = destSize.x/2.0;m_srcTY = destSize.y/ 2.0; What do m_srcTX and m_srcTY mean? and why destSize.x and destSize are divided by 2.0? 2. In SpaceTransform.cpp, a variable named params.distance appears many times. What does it mean? 3. What is the function AddTransform in SpaceTransform.cpp used for? Thanks for your help! -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
Re: [hugin-ptx] Re: Command line interface for hugin please
Didn't I just say something about some documentation being a bit ... sparse? Please, all you programmers out there: Take an additional hour or so, after you are done with the Real Work, and expand the help and man files. Then take yet another hour, go back over your code and add some comments. (Well, really, you should be commenting as you go. Shouldn't you?) Coolness isn't cool if nobody but yourself and three buddies can use it / make sense of it. Come on now, everybody reach for the next level TOGETHER. ;) Thanks, eo On Nov 21, 2010, at 10:18 AM, kfj wrote (in part): I looked at likely candidates among the scripts that handle pto files, but all I found was extremely meagre documentation. It made me really angry. Like there is 'hugin_stich_project'. It is a command line tool to stitch a hugin project. It states Verwendung: hugin_stitch_project [-h] [-o str] [-t num] [-d] [project images...] -h, --helpshow this help message -o, --output=stroutput prefix -t, --threads=num number of threads -d, --delete delete pto file after stitching ... and that's it. (there is a man page which says the same in slightly more words). . . . I lost patience. with clenched jaw from grinding my teeth Kay -- -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
Re: [hugin-ptx] Re: Command line interface for hugin please
kfj wrote: I have used awk/gawk a lot when I was still working as a programmer, so I can probably help if your efforts become more involved. awk is much more powerful than just changing a few words in a bit of text. Everyone who's into scripting would do well to learn at least a bit of it; many tasks that seem daunting otherwise become very easy indeed. Awk is really good at text processing, but that is also it's main scope. As a general purpose language it becomes a bit awkward. If you want a tool that can do everything awk does plus everything else you'd expect from a programming language, go for Python. You won't regret it. In Python you can also use regular expressions to pick out bits of text and then change them to something else; since it's general- purpose, it's more verbose but also much more flexible. back in the day (g)awk was useful (and I used it). However, with perl now so mature and widely installed (or installable) I view awk as of historical interest only. I use, and would recommend, perl as a scripting glue language. Perl has a helpful combination of syntactic convenience and a huge library of pre-cooked code. BugBear -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Re: Command line interface for hugin please
On 22 Nov., 10:53, paul womack pwom...@papermule.co.uk wrote: back in the day (g)awk was useful (and I used it). it is still on every UNIX-like system, ready to go. Ubiquitous. Allowed me to just write a five-liner to be run from the shell to make my point. However, with perl now so mature and widely installed (or installable) I view awk as of historical interest only I use, and would recommend, perl as a scripting glue language. I use, and would, and did recommend Python as a scripting language. I suspect perl is as powerful. Python got me first. And as far as (most?) Linux systems go, Python is already there - no need to install anything. Perl has a helpful combination of syntactic convenience and a huge library of pre-cooked code. I had a good look at Panotools-Script. I can only subscribe to what Eric O'Brien wrote above. It may be extremely cool code, but I found it very hard to figure out what it actually did. I feel that Python is more legible. with regards Kay -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] Python pto parser
Hi all! I've come to a point with my Python pto parser project where I have a functioning scanner which can handle all pto syntax I'm aware of and presents the scan as an object containing the pto file's content in a structured form to be analyzed and modified. The scan is syntactic so far, and it deliberately recognizes a superset of pto to be quite future-proof. It does not check if the scan makes sense semantically. Semantics aren't necessary, though, for a lot of operations on the pto data, so I want to keep the scanner accessible as a separate entity anyway. I would like to publish the code for peer review. I don't know how to go on about publishing. Is there a designated space in the hugin dataverse to upload stuff like this? Maybe one of the developers could give me advice? I'd rather have the project hatch in the community than going ahead and putting it on PyPI already. The code is plain Python, licensed GPL. with regards Kay -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
[hugin-ptx] ANN: The new tracker is up
Hi Hugin community A milestone has been completed and the new tracker is up on Launchpad (LP) at [0]. Thank you SourceForge (SF) for nurturing our project in the past seven years. Source code repositories, downloads, and the official Hugin website stay at SF. Tickets are now accepted at LP. However there is still a lot of work to do. This is a short summarized announcement. Longer mails with nitty gritty details for the specific stakeholders will follow later (but don't wait for them). The following is summarily addressed in this announcement: * organization * accounts * groups * communication * documentation * next steps 1. ORGANIZATION The Hugin on LP infrastructure [1] is temporarily owned by the Hugin PPA Packagers [2] team. We'll transition ASAP to mirror the SF project structure. The Hugin Developers team [3] has been created to own the infrastructure. The charter is the same as for the current SF project [4]. A new Hugin Bug Hunters [5] team has also been created to use the expanded LF functionality. See section GROUPS below. Both teams are moderated (more open than SF's restricted groups). To be added to a team: either subscribe yourself (new and improved!) or let your LP ID be known here and an admin will add you (like on SF). 2. ACCOUNTS The tracker is world-readable. An LP account is required to write into the tracker (like on SF). if you don't have one yet, please create an LP account. Extra bonus if you can document your steps and publish them here (see below DOCUMENTATION section). If you've filed reports in the old tracker, you will need to complete an extra step of claiming your account. An LP admin will merge your accounts. I have still to do this myself and will document the process (unless somebody else is faster). 3. GROUPS Membership in a team grants privileged access. Ideally every person with write repository access on SF should become a member of the Hugin Dev team [3]. New: triaging and prioritization of tracker tickets will be delegated to a formalized group: the Hugin Bug Hunters team [5]. Power users are encouraged to become members. The same charter as Hugin Devs apply. 4. COMMUNICATION Every LP group may have a single mailing list. To mirror the current tracker on SF, tracker notifications will be sent to Hugin Bug Hunters. I am not sure yet if developers should subscribe to Devs and Bug Hunters separately, or if we simply subscribe Devs to Bug Hunters. I tend for the first approach, so that each Dev can control if they want to be notified about bugs or not. It better reflects current status. 5. DOCUMENTATION Like with every process that is new and will be undertaken by many people, documentation by the early adopters will help sooth the pains of the followers. I am currently writing a documentation on how to get the most out of LP. However, since I have had an account for long enough, I can't document account opening. Can some user please be so kind and document a step by step account opening? 6. NEXT STEPS The Hugin on Launchpad infrastructure still need some TLC. I've just added our release cycles as series (2010.4 is there, just marked as future so it only shows when showing full history. Next I shall add betas and release candidates as milestones, so that bugs can be assigned / related to them. After enough people have opened / linked accounts; and have registered for the privileged access groups; there are 398 currently active tickets that needs to be triaged - i.e. reviewed and assigned a status different than new. It will be a while until the tracker develops its full potential, and we'll learn along and adapt to make the best out of it. Thank you all for your continued support. Yuv [0] https://bugs.launchpad.net/hugin [1] https://launchpad.net/hugin [2] https://launchpad.net/~hugin [3] https://launchpad.net/~hugin-devs [4] http://hugin.sourceforge.net/community/charter/ [5] https://launchpad.net/~hugin-bug-hunters signature.asc Description: This is a digitally signed message part.
Re: [hugin-ptx] Python pto parser
Hallo Kay, On November 22, 2010 08:39:41 am kfj wrote: I would like to publish the code for peer review. I don't know how to go on about publishing. Is there a designated space in the hugin dataverse to upload stuff like this? Thanks for intending to share. The earlier the better. I will open an extra Mercurial repositories in Hugin for scripts and other contributions. It can always be merged into the main repo later on if it makes sense. You will need to tell me your SF user ID so that I can grant you write access to the Hugin project. If you don't have yet an SF user ID, open first a Launchpad account (and document it please). Then you can use OpenID to log on and create an account on SF. Theoretically it should be simpler than creating a new account from scratch. I'm interested in a documented experience. Opening a repo is a matter of a minute or two, so I'll wait until you communicate your SF ID here. Welcome to the team! Yuv Maybe one of the developers could give me advice? I'd rather have the project hatch in the community than going ahead and putting it on PyPI already. The code is plain Python, licensed GPL. with regards Kay signature.asc Description: This is a digitally signed message part.
[hugin-ptx] that was fast!
Thomas Modes was faster than lightning. He's now admin of both LP teams. The Hugin Developers team (currently Pablo, Thomas, Lukas, and myself) are now officially owners of the Hugin on LP infrastructure. When joining the two groups, please bear with us as the mailing lists are still set to defaults and there may be a higher volume of mails than wanted, especially with all new joiners and changes to their status to admin. Yuv signature.asc Description: This is a digitally signed message part.
Re: [hugin-ptx] that was fast!
On November 22, 2010 05:26:45 pm michael crane wrote: Do I hear a YES ? [0] [0] Oh I want it so bad I hear you. A little bit of patience. We all want that. For now all I can say is that Santa Claus is coming soon. Given how poor we are, this means a *source* release. There can't be a binary release before a source release anyway. Given how many people/resources have been gravitating toward building and testing binaries in recent releases, maybe the time between the source and the binary release can be further shortened. And as far as *all* platform goes: there won't be support for Android or iOS (it has not even started yet) and I doubt anybody will want to spend time trying to make the latest code work on Windows 98 despite the fact that it was a hugely popular platform once upon a long ago. So you will excuse me if I lower your expectations, and say that we do whatever effort we can to have the source code build on the main supported platforms - a definition that changes over time and depends on the resources available to the project; and that we strive to have quality builds available for said platform, and that this too is a matter of time and resources. All I can promise from my side is that I am working on: - getting the migration to the LP tracker done - cleaning up the visual appearance of the app (Cristian's design has been waiting for too long) - getting a source release out before Christmas (first beta likely toward the end of the week, to start drumming up support from the builders on the different platforms) - getting a robust build infrastructure for distribution on Ubuntu. Lucid, and Jaunty (work already, is just a matter of time that I don't have). Maybe Maverick (though I am afraid breaking my workstation in the process of upgrading and I need it for work too. And over Christmas I won't have access to my HTPC on which I do the rather experimental creepy stuff, so maybe Maverick and Natty will be for early January). - getting the source package produced approved so that they will flow into the official Natty release 11.4 (by then we might have another release and the Hugin PPA will take up where the Ubuntu distro left). That said, I still have a family (and my son just told me that supper is on the table) and a life, so no matter how badly you want it, I may not be able to give it to you and I won't apologize for that. Yuv signature.asc Description: This is a digitally signed message part.
Re: [hugin-ptx] Re: Claiming an SF account in LP
On Mon, November 22, 2010 10:44 pm, Yuval Levy wrote: On November 22, 2010 03:55:40 pm Bart van Andel wrote: It's really a shame that Launchpad only implements the provider part of the OpenID protocol, and not the consumer (relying party) part. yes. I know from other sources that they are reviewing their whole sign-up / log-on architecture. Since it is critical they don't want to make mistakes. Think for example of a spammer setting up an OpenID provider (plain simple, takes less than 10 minutes) and using it to generate tons of spam-accounts. They are experimenting with things and collecting data / observations of how users interact. With such a large platform, they can't be as nimble as they would like to. As long as I don't need the account, I'll wait Waiting is fine. You'll need an account if you want to use the tracker, including voting for that issue to get fixed by hitting the this bug affects me too button ;-) Well, strictly speaking, the Hugin PPA team (binary builders, not to be confused with the development team, even if some people may be part of both) is using Launchpad and its build infrastructure (Soyuz) to build packages for Ubuntu Linux. This is currently unfinished / incomplete job. There is a feature of that infrastructure which I would like to tap to produce nightlies. When everything works as advertised, LP can import the latest code from external repositories. Provided with a recipe it can bake binaries automatically. Think of it as on-demand builds of the bleeding edge. No manual intervention. RAWstudio makes use of it and I get my nightlies as regular as the commit mails from heir (self hosted) SVN repo. I have two objectives for the Hugin PPA: 1. provide subscribers with the latest stable releases for all currently supported versions of Ubuntu; 2. and with the latest bleeding edge nightlies. Currently (1) is only partially implemented thanks to Philipp Seidel. Although there is a report that dependencies have not been specified too well what is all this ? are there maintainers for each distribution ? I guess they have some headaches yum install hugin ah! cool it works can somebody get a grip on this project so that people [2] can work with it ? thanks mimmik [2] lots [0] https://bugs.launchpad.net/bzr-hg/+bug/674581 -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
Re: [hugin-ptx] that was fast!
On Mon, November 22, 2010 10:59 pm, Yuval Levy wrote: That said, I still have a family (and my son just told me that supper is on the table) and a life, so no matter how badly you want it, I may not be able to give it to you and I won't apologize for that. as I understand things you are not such a hot coder so why are we waiting on you ? regards mick -- You received this message because you are subscribed to the Google Groups Hugin and other free panoramic software group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx
Re: [hugin-ptx] that was fast!
On November 22, 2010 06:17:38 pm michael crane wrote: as I understand things you are not such a hot coder so why are we waiting on you ? good question indeed. why are you waiting? Yuv signature.asc Description: This is a digitally signed message part.
