Datasets:

Hieuman
/

gmane_dataset-doc

Modalities:

Text

Formats:

Size:

Libraries:

Dataset card Data Studio Files Files and versions Community

Dataset Viewer

Auto-converted to Parquet

Split (1)

train · 4.53M rows

authorIDs large_stringlengths 5 166	fullText stringlengths 161 97.2k
[email protected]	OK, that's interesting. I only suggested that as a hack. (The hack would be to do something like "J:7 N:4 K:2" as the comment.) Very cool. Did you/do you use it? I hadn't thought about that... I don't think I'm worried about it. By the time my kids are that sophisticated I hope to not be censoring them any more. We'll see if it works out that way. I see. That would be a smart start. Is it handy? I'm interested.
TENY/[email protected]	I have a 1-Wire net with a number of weather instruments on it. Recently I have been getting counter errors on both the rain gauge and lightning detector. Earlier I was getting false positives with the lightning detector. Thanks to some suggestions on this list I was able to resolve that by relocating the detector. None of the other instruments on the net seem to have any problems. I am not getting false counts, but rather I am seeing invalid reads of the counter. The log file (see sample below) will show normal values, then suddenly show an unbelievably high count, then go back down to its previous normal count. Occasionally, the count may go down and then back up again. The rain gauge seems to do this about once per day, not at any particular time. The lightning detector does so maybe a half dozen times per day. I can't say for certain whether it is a hardware or software problem. I had been running a 32 bit binary of owwnogui on a 64 bit CPU. I recently recompiled with a 64 bit compiler and have observed that the erroneous values are now MUCH larger. That makes me suspicious of an uninitialized storage issue, but this also seems unlikely as I know lots of people are using this software and probably are not seeing this. System logs do not show any errors related to these problematic values. Any suggestions or insights would be appreciated.
344L/[email protected]	I'm working on an iOS app that allows people to turn specific channels on or off while playing videos with surround audio tracks. I'm using kxmovie ( https://github.com/kolyvan/kxmovie) as the base for it. The render callback on the audio unit is currently calling swresample, which is remixing sound to match the 2-ch output of the Apple remote I/O. As you probably know, different audio codecs encode their channels in different orders, so I can't just always ask for the second channel in an audio track, for example. Is there a way for me to get a specific audio channel in mono (e.g. ask for surround left and let ffmpeg figure out which one it is for the selected codec) or to get it to set a default channel order and reorder it if the format doesn't match it (which would then allow me to always point to the same channel number if I want the surround left channel, for example). Right now this is the code I have for the buffer: Can you help me out? Thanks!
[email protected]	I already tried to do that, but it didn't work. PostGresQL return me a ERROR saying that the syntax was invalidates. But thank you even so for the help. I have never done any of this, but looking at your code, it seems that you would want to change the select in the stored procedure to something like: This should only return the full user name as desired, I think. Unless you are wanting something more "generalized", so you can do 'SELECT *', then isolate a column (any one of them, however many there are) from the result set - I am certain there is a way to do it, but having never played around with this, I am unable to offer much more advice. http://archives.postgresql.org
t/[email protected]	In earlier versions of KDE and kmail, I could select one or two folders for threading messages as these folders often contained replies and related where I want to follow a thread. However, in other folders it is more useful for me to latest received message and sometimes I want to change the sort order and perhaps just list them in terms of sender. I notice that now if I change the grouping or sort order in one folder it changes throughout all the folders. Is there a way to set the view on a particular folder and not have the new setting taking a global effect on kmail. Currently using KDE 4.4.1) "release 228" and Kmail Version 1.13.1
t/[email protected]	Three machines all use cups (SuSE 8.0) and have lpfilters etc removed. I can use lpr on two of the machine (/usr/bin/lpr). The third reports command not found (ie /usr/bin/lpr doesn't exist). There are times when I need to use lpr on the third machine. How can I find out what package it belongs to? Does anyone know where it lives on the SuSE 8.0 distro? Would be very grateful for any help or pointers.
t/[email protected]	I did yet another re-install of windows98 on my system. I used my DVD to boot into linux (SuSE 8.0). Then I ran Yast2 (the bootloader configuration option) to reinstall lilo. It completed successfully(?) but nothing was written to the MBR. I repeated the process with the same result. I remember in the past I had the same experience and at that time (not being the brightest spark) I reinstalled my SuSE 8.0 just to get lilo sorted. This time (with a flash of inspiration) I ran lilo from the commandline and it worked perfectly. Has anyone else had this experience? Is this a bug in Yast2, or did I do something wrong or omit something? Perhaps Yast2 isn't supposed to write to the MBR? I have two drives hda and hdb. Windows98 is loaded on hda and SuSE 8.0 on hdb.
t/[email protected]	http://bugs.kde.org/show_bug.cgi?id=100093 I think this may be related. I'm using KDE 3.5.1. Have a remote calendar with write permission on group. However, if anyone other that the owner edits the file the calendar will not save. No crash of the system only a failure to save the file. Other than that is seems the best choice for our purposes. Unfortunately, the need for a calendar to be editable by more than one person is critical.
N/[email protected]	היי גיא, דיברתי עכשיו עם אייל מ XLN M3 10mm שהוא שבארץ זה עולה 11 אגורות ובחנות בסין זה עולה 9 סנט. אני מקווה שזה יכול לעזור לך גיל Also isn't is better to keep the shipment cost low to reduce the chances of passing through customs and adding extra % on the price? IMHO we do, and I can define the BOM, but even 50$ will be nice. also, maybe some people want to order hardware for their personal use, in which case not all the 200$ will be for TAMI. Does TAMI need $200 worth of screws?If we actually do, and some can define a BOM, I'll ante up part of the cost. I'm in urgent need of a large bunch of standoffs and other screw-type hardware for a project, which are either expensive and/or unavailable locally. Therefore, I'm going to make an order from an AliExpress shop and use express shipping (FedEx / DHL etc). The nice thing is that they provide FREE FedEx/DHL shipping for orders above 300$. However, I only need about 100$ worth of stuff. I thought if any of you want to join in, then we can combine orders and enjoy the free shipping. The particular seller looks quite reputable (although I haven't tried them yet personally) and the prices are good. Here is their store: http://www.aliexpress.com/store/219903 If you want any stuff, reply (either to the group or to me privately) with a list of links to items and specify qty, plus expected total (disregard the shipping cost). I plan to make the purchase in 24-48 hours since it's urgent. also, if you want to donate some screws hardware to TAMI, let me know - either the specific items or just the donation amount, and I'll do that. כדי לבטל את הרישום לקבוצה הזו ולהפסיק לקבל ממנה דוא"ל, שלח דוא"ל אל [email protected]. כדי לפרסם בקבוצה הזו, שלח דוא"ל אל hzZls1AlzB+2QJ8/@example.com. לאפשרויות נוספות, בקר ב-https://groups.google.com/d/optout. כדי לבטל את הרישום לקבוצה הזו ולהפסיק לקבל ממנה דוא"ל, שלח דוא"ל אל [email protected]. כדי לפרסם בקבוצה הזו, שלח דוא"ל אל hzZls1AlzB+2QJ8/@example.com. לאפשרויות נוספות, בקר ב-https://groups.google.com/d/optout. כדי לבטל את הרישום לקבוצה הזו ולהפסיק לקבל ממנה דוא"ל, שלח דוא"ל אל [email protected]. כדי לפרסם בקבוצה הזו, שלח דוא"ל אל hzZls1AlzB+2QJ8/@example.com. לאפשרויות נוספות, בקר ב-https://groups.google.com/d/optout. כדי לבטל את הרישום לקבוצה הזו ולהפסיק לקבל ממנה דוא"ל, שלח דוא"ל אל [email protected]. כדי לפרסם בקבוצה הזו, שלח דוא"ל אל hzZls1AlzB+2QJ8/@example.com. לאפשרויות נוספות, בקר ב-https://groups.google.com/d/optout. כדי לפרסם הודעות בקבוצה זו, שלח דוא"ל לC9/[email protected]. לאפשרויות נוספות בקר ב-https://groups.google.com/d/optout.
[email protected]	Thank you, Simon for fixing the bug ORCHESTRA-13, but this takes me to my next problem: I explain a situation that is not the normal case, but it can happen: First, a user should not try to edit more than one product in the same conversationContext, because a conversationContext can only include one conversation of the same type. Right? myfaces-orchestra-examples-project - PetStore: If a user open a new browser tab or window e.g. by clicking "open link in new tab" he gets two windows with the same conversationContext, then 1. Tab1: press edit "product A" 2. Tab2: press edit "product B" 3. Tab1: save "product A" Finally the object "product B" gets all the attributes of object "product A". Bad! What options are there to prevent this? I have two solutions: 1. Using the separateConversationContext Tag 2. Using a pageFlowScope to store the objects What do you think? (do a SVN check-out)
[email protected]	Hi Karl. Very thorough IR! I have several edits and a few comments below, mostly minor stuff. Our policy is to upload the html version of each report to the Test folder at BGT.org and provide a link so the monitor can also look at the html version. I would appreciate it if you would send me an e-mail with the link when you have it uploaded to the Test folder. Thanks! Will. I also compared it to the light coming from my other headlamp with suprising results. EDIT: surprising I was initially intruiged and impressed by the quad. EDIT: intrigued The clips and folds that allow the headband to be adjusted for diferent head sizes seemed overdone, as if the manufacturer wanted to ensure that it would be wearable long after it stopped functioning. Upon further examination, Every setting was brighter than the same relative setting on my other headlamp. EDIT: every (unless you mean for it to be emphasized with the capitalization). While being worn, the large clips on the band were intially annoying, digging into my skull but I knew from experience that it was a temporary sensation and quickly subsided as predicted. It was my belief that if any activity was good at testing the effectiveness of a headlamp it would be scavanging. The wide scope of the bright field of vision is far superior to my other headlamp, and all the other headlamps that were at the campsite that night, but the projected beam was not at focused as a hand held torch that another hiker had brought that night. EDIT: as focused When looking at objects about 1 to 2 m away, I found the beam to illuminate everything I could see, even those out of the very corner of my eye. Q: How easy is it to turn on and off, and change the brightness setting? A: relatively easy. all functions are routed through a single button on the top of the housing, covered in bright orange/yellow rubber. EDIT: All functions Q: If the headlamp is worn for long periods in heat, the elastic band will absorb sweat and retain body odor. Given that the housing is waterproof to 1 m and impact resistant, can it be safely washed in a standard washing machine? If not, can the band be removed from the housing so the band can be washed? EDIT: Need English equivalent Q: Does headlamp light reflect off the lamp at close range to see it? A: Somewhat. A significant amount is absorbed by it's black/grey colour, but if the on/off/setting button is in a visible position the orange rubber is quite visible. Also, the L.E.D. cavity is reflective silver with a clear plastic cover, both of which can be very reflective. Q: Does headlamp light reflect off the material at a distance to spot it? A: Somewhat. See above. I will attempt to determine the range at which it can be seen in different positions. Q: How easily are they to see in the dark from a distance? A: Impossible. The material does not glow in the dark, or create or emit its own light of any kind when turned off. COMMENT: In these three questions, it is not clear what you are talking about. Could you re-phrase to make it clearer? The Quad is also lighter thanother headlamps of similar design, but the shape and size could be redeveloped. EDIT: than other I expect it will gradually wear to the point where the slightest movement will cause the housing to fall on my forehead, away from the band. COMMENT: This is projecting, suggest you delete this sentence and let the previous sentence suffice. Easy to put on and take off EDIT: repeated statement Less than spectacular reputation COMMENT: This seems to jump out of the blue. I suggest that you limit your report to your experiences and your observations.
[email protected]	Hi Chuck. Here are a few edits and a comment for you to consider. Your html version looks great and the photos really enhance the report. Go ahead and upload when ready and be sure to delete your report in the test folder. Thanks! Will Rietveld, Test Monitor. I have continued to wear the Tifosi Q3 sunglasses almost on a daily basis. I have worn them on several recent day hiking trips and a morning trail run. Not much has changed since my field report. COMMENT: Could you estimate the actual number of day hikes you wore them on? It would be nice to be a little more specific on the amount of actual use. Occasionaly I would have a drop of sweat drip on the lens and I simply wipe the lenses with the micro-fiber cleaning bag and continue my run. I decided to insert the AC Red lenses for better visability. The red tint really makes it easy to see in foggy weather and it appears to make objects more clear and bold. The mist from the fog tended to build up on the lenses and I basically wipe them with my finger which made the visability a little bit more obscure. This didn't cause too much of a problem as I could still see where I was going and again the tint helped the obscured visability. EDIT: visibility (3 places) They also stayed snug to my face and never felt to tight or gave me a headache from wearing them during long periods of time. EDIT: .felt too tight. I actually wrecked on my bike and the glasses stayed in teh original position and never came off. EDIT: .glasses stayed in their original position. I can't stress enough how much the Tifosi Q3's have held up in durability and have comfortable they have been. EDIT: ...and how comfortable they have been. The great thing is that the lightweight of the glasses lets the user have continuous eye protection from the sun's UV rays and not feel the glasses on the face feel any fatigue from them. EDIT: .glasses on the face or feel.
[email protected]	Hi Coy, looks like you got to use the Volt in some cool weather before it got hot. I have a number of edits below for you to consider. I also looked at your html version in the Test folder; nice format, and thanks for including some photos. When you upload, be sure your hyperlinks work, and delete your FR in the Test folder. Thanks! Will * 1/2 Zippersloft EDIT: Zipper Field Testing Locations and Conditions I used the Volt with my hammock the first five nights and the remaining one night inside a 2-man tent. I used the Volt the first two nights in the woods here in Northeast Alabama. The next three nights were during 4 day, 36-mile (58 km) hike on the Appalachian Trail in Georgia. EDIT: This is not very clear, and doesn't add up. Is it 5 or 6 nights? Suggest you re-write this. Field Test Test Results EDIT: Word repeated. My first night in the Volt was uneventful. It dropped down to 52 F (11 C) but I was neither to hot nor to cold (think Goldie Lock's potage). EDIT: too hot A few nights later I was pleased but not surprised that the Volt kept me warm on the coolest nigh I had opportunity to use it (44 F (7 C). EDIT: night, an opportunity As I planed a hike to the mountains of North Georgia I was hoping for cooler testing weather and just missed sub-freezing weather by two weeks. EDIT: planned As a result I cannot really comment on how the Volt will perform in cold weather and obviously not down around the temperature it is rated for, ie 15 F (-9 C). EDIT: i.e., This plus the slight opening the hammock creates at the head end probably allowed me to stay reasonable cool. EDIT: reasonably On the 3 nights on the AT when the lows were around 58 F my head stayed outside the sleeping bag (the hood was actually hanging below me). EDIT: we usually spell out numbers under 10 (you do elsewhere), need metric equivalent I even noticed that occasionally I had both arms outside the bag but with most of the bag pulled up to my about my neck otherwise. EDIT: delete "my about" On advantage of using the Volt over my hammock is my bag never really touches the ground. EDIT: One advantage I have stored it in the generously sized storage sack between trips but it did spend 4 days in the provided stuff sack which by the way is sized large enough to make stuffing it a reasonably easy chore. EDIT: four days Dislikes so Far *None really, other than the fact that I was warmer on the last night than was comfortable. Again, this was not the bags fault. EDIT: bag's As a result, I will just use the bag, leaving it open as much as possible, and hope the foot ventilation allow me the make it. EDIT: This is an awkward sentence. How about "As a result I will use the bag with it open as much as possible, and hope the foot ventilation allows me to stay comfortable."
[email protected]	I finally got a response to my e-mail to Bushnell tech support, and got the following response: "Thank you for contacting Bushnell. Our software engineers are aware there is an issue with the elevation reading in yards instead of feet. They are working on a software update that you will be able to load off of the www.bushnellgps.com". Looks like we should be able to keep our present units and update the software when they have software update.
[email protected]	Hi Ben, I posted my edits to your LTR on the BD Enduro trekking poles on Sept 9 (msg 23250) and I notice that you have not reposted your revised LTR as I requested. Your report was missing some required sections and you did not upload your html report to the Test folder. Please repost asap so we can complete this test. Thanks, Will Rietveld Test Monitor.
[email protected]	Hi Sam. Sorry for the delay, I have been gone on a trip for 9 days and just got back home. Nice job on your report, and great photos. I have a few simple edits for you below. Go ahead and upload when ready and be sure to delete your report from the test folder. Thanks! Will Rietveld, Test Monitor. Listed Size: 1 9/16" x 9/16" (4cm x 1.4cm) EDIT: Add a space between the number and the unit. (easier to read) I fill that this was a brilliant move on Nite Ize part. EDIT: feel First time trying the S-Biner was very uneventful. I took it out of the package, clipped it on my backpack, clipped my hat on to the other side and was finished with my fist test. Very simple and satisfying to use. EDIT: My first time. EDIT: .finished with my first test - very simple and satisfying. I took the Figure 9 out of the package, opened the package and followed the clearly printed instructions. EDIT: Took it out of the package twice? How about: "I took the Figure 9 out of the package and followed." I was able to follow the instructions the first time through and was successful in tightening a rope with out any knots. Can I use them in various ways as easily as it looks on the manufactures website? EDIT: manufacturer's
[email protected]	Hi. Here is my IR for editing. The html version is in the TEST folder at: http://www.backpackgeartest.org/reviews/test/TESTS/IR--Spenco%20Backpacker%20Footbeds--Will/ Thanks in advance for editing my report. Will I have been an avid backpacker for 47 years. I am retired and backpacking is my passion. During the summer I backpack nearly every week. During the fall, winter, and spring I backpack, day hike, snowshoe, or ski every week. I backpack in wilderness areas in Colorado, Utah, New Mexico, Arizona, and occasionally in other western states. Backpacking Style-I have been a lightweight backpacker for 30 years, an ultralight backpacker for six years, and have been experimenting with super ultralight backpacking for three months. My wife and I give presentations on ultralight backpacking in our local area, and have developed a website called Southwest Ultralight Backpacking (http://home.bresnan.net/~swultralight) to share information. PRODUCT INFORMATION (photo) According to the Spenco website, "the Spenco® Outdoor Adventure Series is a new line of footbeds that are designed specifically for the needs of outdoor enthusiasts. The unique combination of stability and cushioning provides the outdoor enthusiasts with the benefits needed to experience more - more comfortably." The Spenco® Backpacker model "is for outdoor enthusiasts that are carrying heavy packs over unpredictable terrain for multiple days at a time. This intensity of outdoor participation needs a footbed with extra cushioning, support and the additional benefit of motion control to help you experience more - more comfortably." Product features are (according to information on the box the footbeds came in): OAST Stabilizer-a raised area on the inside edge of each footbed helps provide better support and stability. Cool DryT Technology-the wicking fabric on the top side helps to keep feet dry, to reduce hot spots and blisters. PolySorb ShoxT-raised foam pads on the underside provide extra cushioning to absorb shock and help prevent over-pronation. INITIAL IMPRESSIONS-The Spenco Backpacker model is indeed a heavy-duty footbed compared to the footbeds that came with my boots (Dunham Terrastryders) and the Superfeet Performance Insoles (green) that I have been using for some time (right photos). The Spenco Backpacker Footbed is clearly thicker. It has a lot of extra foam cushioning on the top and bottom and more lateral support on the inside edge. The thicker footbeds will probably affect how my boots fit, mostly in terms of volume. Their stiffness is much greater than the original insoles and about the same as the Superfeet. It definitely appears that the Spenco Backpacker Footbeds will make a difference in how my boots fit, feel, and perform. WEIGHT-The Spenco Backpacker Footbeds are a bit on the heavy side, 6.1 oz (173 g) per pair, compared to 3.5 oz (99 g) per pair for my Superfeet insoles, and 1.3 oz (37 g) per pair for my original insoles. For ultralight backpackers, who try to minimize boot weight, the extra weight of the Spenco Backpacker Footbeds is a significant factor. Interestingly, the left footbed weighed 0.3 oz (8.5 g) more than the right one. INSTALLATION-The directions on the box say to remove the old insoles and replace them with the Spenco Footbeds, trimming them with a scissors if necessary. I found that I needed to trim about ¼-inch (6 mm) off of each footbed to get a good fit. CLEANING INSTRUCTIONS-"Hand wash with warm water, air dry." TEST LOCATIONS AND CONDITIONS-I backpack nearly every week, so the Spenco Footbeds will see a lot of trail days in the next four months. Between backpacking trips I do numerous day hiking trips in the local Colorado Mountains. This fall I will be backpacking and day hiking in the canyonlands country of Utah, Arizona, and New Mexico. I am an ultralight and super ultralight backpacker. My total pack weight is usually 10-20 pounds (4.5-9.1 kg), so the Spenco Backpacker Footbeds will not be used for real heavy-duty hiking conditions, in terms of weight. However, I do a lot of off-trail backpacking in really rough, steep conditions, so the footbeds will be subjected to some challenging conditions from that standpoint. The testing environments will consist of: badlands desert, canyon country, forests, and high elevation alpine country. Expected extreme conditions include: snow storms, strong winds, dust/rain storms, heavy rain, intense sun, low temperatures, and high elevations with strong UV and intense thunderstorms. Terrains will be forest and desert trails, slickrock hiking, off-trail bushwhacking, scrambling, walking in water and mud, and hiking in snow. HOW THE FOOTBEDS WILL BE USED-The Spenco Footbeds will be in my hiking boots every time I go out, which averages 3-4 days a week. I will put hundreds of miles on them in all types of terrains and conditions. On each trip I will take a thermometer with me to measure the actual temperature so I can relate it to my comfort level while using the Spenco Footbeds. In my notes for each trip, I will record the following data in relation to my comfort wearing the Spenco Footbeds: 1) temperatures, 2) estimated wind speed, 3) estimated humidity, 4) altitude, 5) precipitation (including what form), 6) trail (or no trail) conditions, 7) how the Spenco Footbeds were worn (boots used, type and number of socks, with or without gaiters, chaps, or rain pants), 7) my exertion level, 8) my comfort level in terms of how warm/cold, wet/dry, or cramped/comfortable my feet feel while using the Spenco Footbeds, and 9) any foot problems (blisters, hot spots, foot fatigue) that I had on each trip. FACTORS EVALUATED-The specific factors I will be evaluating the Spenco Footbeds for are as follows: MATERIALS, QUALITY AND CONSTRUCTION: Do the footbeds use high quality materials, and are they well constructed? FIT: How do they fit in my wide boots? How much do they change how my boots fit, in terms of roominess in the toe box, actual width, heal counter width and support, and lack of heel lift? How good is the arch support? How do they affect boot volume? COMFORT: Are the footbeds adequately padded for comfort? Are the footbeds adequately contoured and supportive? How do they work with pronated feet? How comfortable are they on different terrains, eg on rocky trails? How well do they maintain foot comfort and avoid blisters or other foot problems on high mileage days? (Note that most any footbed is comfortable for a "normal" 6-8 hour trail day, but hiking 12+ hours and 20+ miles/day is a different story.) Are they comfortable to wear in hot weather? Do the Spenco Footbeds provide better support and cushioning to make off-trail hiking in rocky terrain and steep downhills and sidehills easier on my feet? USABILITY AND PERFORMANCE: Do the footbeds need trimming before I can use them? Are they easy to put in/take out? How do they affect boot stiffness, arch support, and heel cup snugness? On performance the main issues are foot comfort, and avoidance of foot fatigue or foot injuries (blisters, hot spots, etc). This will be a great comparison, because I am now having foot problems after high mileage days in the Terrastryders. Will the Spenco Footbeds eliminate these problems? DURABILITY: I do a lot of bushwhacking and off-trail hiking. How well do the footbeds hold up under constant rough use? Are there places where they come apart? How well do they hold up with repeated wetting and drying? What is their expected life span? I will test the Spenco Footbeds to determine whether the following expectations are met or not. 1) The Spenco Footbeds will be high quality and will not show any excessive wear, de-lamination, or other deterioration during the four-month test period. 2) The Spenco Footbeds will readily fit in my boots, and will not significantly change the sizing of my boots. If it does change the sizing, I can readily adjust for it by using thinner socks or other means. 3) The Spenco Footbeds will provide noticeably better foot comfort over a variety of terrains and conditions. I will not have any discomfort or fatigue that is caused by the footbeds. 4) The Spenco Footbeds will improve the performance of my boots, by means of better arch support, better lateral support, and proper stiffness. Better performance can be measured in terms of better foot support on steep slopes and rocky terrain. 5) The Spenco Footbeds will minimize foot fatigue from hiking on rocky trails and on high mileage days. I would like to thank the Spenco Corp. and the Backpackgeartest Group for selecting me to participate in this test.
[email protected]	Hi Chuck. Here are your edits, mostly just clarification issues. I also looked at your report in the Test folder. Make the revisions and you are good to go. Thanks. Will Pole: 8 oz (227g) EDIT: Need a space before g Field Report EDIT: These links to previous reports are helpful, but 2 paragraphs below it you again use the term "Field Report", which is confusing. Shouldn't the latter (2 paragraphs below the hyperlinks) be "Long-Term Report"? However, on the other trip, I experienced high temperatures, rain and high humidity. EDIT: For clarity, need a comma after rain. This trip was in the valley of the Caesars Head state park. EDIT: Valley of the Caesars State Park. Needs to be capitalized because it's a proper name. The elevation in the valley was 4285 ft. (1306 m) and the temperature was 87 F (30 C) after a nasty thunderstorm that night. EDIT: I Suspect that the elevation had nothing to do with a thunderstorm, so for clarity split this into 2 sentences. I did get some seepage of rain under the edge of the tent. EDIT: Change "rain" to "water". Suggest re-wording to "I did not get any water seepage under the edge of the tent." Since there is not a floor in this tent, it is almost impossible not to get any rain running under the edge with this much rain. EDIT: Change "not a" to "no". Change "rain running" to "water running". I did have a portion of my pad and bag on a piece of Tyvec so they wouldn't get wet if this was to occur. EDIT: Tyvek This is when the evaporation of the rain that made it into my tent started to heat up the inside of the tent. EDIT: Change "rain" to "water". Change "heat" to "steam". Evaporation does not produce heat; it actually absorbs heat. I opened up the top vent and the entry door to let some of the heat out and hopefully cool off the inside. COMMENT: Suggest you say "let heat and humidity out". Good material construction EDIT: Not clear. Great shelter in the colder months COMMENT: Did you test this so you know it to be true, or are you assuming that? If you're speculating on this, you should state it as such. For my area, it was too hot for temperatures above 70 F (21 C) COMMENT: It would be clearer to say ",the tent was too hot.".
[email protected]	Hi Heather. Nice report. I have several comments below for you to consider. Looks like BGT.org is back up, so go ahead and upload when ready. Best regards, Will. Long Term Report Spectrum Brands Advanced Insect Repellant COMMENT: You may want to add the word "Cutter" into the title, as the other testers have. For further product information please read my [link] initial report, and for further anecdotal information please read my [link] field report. COMMENT: I believe the LTR should contain product information and testing conditions. I checked this in the Survival Guide, and the following required information is listed: Product information: Manufacturer, Year of manufacture, URL of top level manufacturer web site (not the item at the site), Listed weight, Weight as delivered How well does it work? COMMENT: You provide a lot of information in this section about the amount and frequency of use and the amount of bugs, but I did not see anything about how it works on different kinds of bugs. Can you comment on how well it worked for mosquitoes, flies, ticks, and chiggers? In Andrew's report he said it did not work on flies in Australia; how did it work to repel flies in the Southeast US? Also, readers would be interested to know if it works to repel chiggers. It is odorless, colorless, does not affect fabrics adversely, did not cause me any skin reactions, containers did not spill or break, the repellant did not feel heavy or greasy, and above all: the repellant did keep insects from biting me. COMMENT: You said above that the product had NO effect on fabrics, so I suggest you take out the word "adversely" (which implies it has some effect).
[email protected]	Hi Andy, looks like you have mastered the new report format. My comments are few. In three places I suggest you break it up the narrative into separate paragraphs for easier reading. Also, there are two places where you need a space between paragraphs so its consistent with your IR. Go ahead and upload when ready, and be sure to delete your report in the test folder. Thanks. Will Rietveld, test monitor. I've also worn this jacket on several ice climbing trips. While it's much too warm to actually climb in, it's proven invaluable while belaying. Even after standing outside in 15° F (-9° C) temperatures for several hours, I stayed quite warm. Whenever I did start to get chilled, I just flipped the hood up and quickly thawed out. I was very impressed by how well the hood fit over my climbing helmet. The only reason that I don't regularly belay with the hood up is because the noise created by the helmet rubbing on the liner material prevents me from hearing my climbing partner well. SUGGESTION: Suggest you make this a separate paragraph, since it's a separate use of the jacket. I also used the Flurry one day while resort skiing. The temperature was hovering around 10° F (-12° C), and the Flurry kept me plenty warm on the windy lift rides. It proved to be too warm for the descents, however. I had to ski with the jacket partly or mostly unzipped, which still wasn't enough to keep me from sweating. SUGGESTION: Same suggestion, make this a separate paragraph. Based on my experiences so far, I would feel comfortable wearing this jacket for an extended amount of time in temperatures down to 10° F (-12° C) when inactive. Frankly, I don't ever see myself wearing this jacket while very active. I personally pump out way too much body heat to justify it. Even while ski touring in -20° F (-29° C) temperatures I simply didn't need to wear an insulated jacket. Maybe I'm just a freak. That said, I would feel comfortable wearing this jacket in -10° F (-23° C) temperatures while moderately active (such as walking without a pack, short bike rides across town, etc). SUGGESTION: Same suggestion, make this a separate paragraph. It's a separate idea, and would make the report easier to read. As a synthetic insulation jacket, it's fairly bulky when stuffed. It takes up more room that I would like, but I found that it actually conforms and packs better when it's not zipped into the internal stuff sack pocket. EDIT: .more room than I would like.
[email protected]	Hi Richard. Sorry I didn't see your post back in early August. I wasn't looking for it I guess. After the long wait, I have only one edit for you below, easy to fix. Your html version looks great. Go ahead and upload when ready and be sure to delete your report in the Test folder. Thanks, and have a great trip. Will I have used the Tablets in the fields on two trips. EDIT: field
[email protected]	Here is my IR for editing. The html version is in the Test folder. Thanks in advance for your edits. Will I don't see this item in the database or the BGT.org website yet. I have been an avid backpacker for 48 years. Backpacking is my passion. In the fall, winter, and spring I backpack in UT, AZ, and NM, and snow camp in the Colorado mountains. In the summer I backpack in several wilderness areas in southern Colorado, and occasionally backpack in the central and northern Rockies. Backpacking Style-I have been a lightweight backpacker for many years and an ultralight backpacker for 7 years. My wife and I give workshops on ultralight backpacking and lightweight food and cooking in our local area, and maintain a website called Southwest Ultralight Backpacking (http://home.bresnan.net/~swultralight) to share information. The Montbell Alpine series is their lightest and most compressible sleeping bags. The Ultralight Alpine Down Hugger #3 is a down-filled sleeping bag rated at 32 F (0 C). Its features are as follows (taken from the Montbell website): 725 fill power goose down is hypoallergenic and resistant to moisture. Shell and lining are 15x24 denier Ballistic AirlightT hollow fiber calendared nylon with DWR treatment on the outside. Vertical baffles maintain the even distribution of down while allowing the down to loft completely. Gathered Quilt System draws the insulation closer to the body and keeps heat in the bag. Full length zipper for easy entry and double sliders for temperature regulation. Draft tube prevents cold air from entering the bag through the zipper. Double compression stuff sack allows the bag to be compressed to a very small size. Bottom Adjustor System is a drawcord at the foot that allows the length of the bag to be adjusted to the user's height, and allows the user to create a "bootie" around the feet for extra warmth. ** Cotton bag provided for longer-term storage The Alpine Ultralight Down Hugger #3 is impressive to look at. The shell is very lightweight, soft to the touch, and apparently downproof. The bag has quite a few features, including a full-length zipper, despite its light weight. When I got inside the bag, I found it has plenty of length and girth to accommodate my frame, plus a few extra clothes for extra warmth when needed. The bag does not have a lot of loft for its temperature rating, and the fact that it is 0.85 oz (24 g) underweight concerns me. I held the bag up to a strong light and discovered that some chambers in the chest area have little or no down. I shook the bag vertically and horizontally and that helped some to distribute the down better. TEST PERIOD-The test will run from mid-April to mid-August 2006. TEST LOCATIONS-Southwestern US (Colorado, Utah, New Mexico, and Arizona). TESTING CONDITIONS-The testing environments will consist of: canyon country, forests, and alpine terrains. Elevations will range from 5000 to 12,500 feet (1524 to 3810 m). Expected extreme conditions include: strong winds, dust/rain storms, heavy rain, low temperatures, and high elevations with strong UV and intense thunderstorms. I expect to test the bag at temperatures both above and below its temperature rating, and in wet and dry conditions. ACTIVITIES-The Montbell Ultralight Alpine Down Hugger #3 Sleeping Bag will be tested in the following activities: 1) backpacking, 2) car camping. SPECIFIC TESTS-I will determine how well the shell's DWR treatment repels moisture and keeps the down dry. I will also test the bag while sleeping under a minimal poncho tarp in rainy weather, again to determine if it sheds surface moisture and stays dry inside. Further, I will sleep in a damp meadow under the stars to determine how well it sheds dew. During the four month test I will use the Montbell Ultralight Alpine Down Hugger #3 Sleeping Bag in several different shelter systems, including a bivy, poncho/tarp, single wall tent, and double wall tent. DATA-On each trip I will record the following data in relation to my comfort sleeping in the Montbell Alpine Down Hugger #3 Sleeping Bag: 1) temperature in my shelter and outside, 2) estimated wind speed, 3) estimated humidity, 4) altitude, 5) precipitation (including what form), 6) sleeping system the Montbell Ultralight Alpine Down Hugger #3 Sleeping Bag was used in, 7) clothing worn inside the bag, and 8) how well it performed in terms of warmth, utility, and comfort. Below are the specific factors on which I will evaluate the Montbell Ultralight Alpine Down Hugger #3 Sleeping Bag. As the test progresses, I will answer the questions I raised in my test application, and update information as needed. 1) MATERIALS, QUALITY, AND CONSTRUCTION: The Ballistic AirlightT hollow fiber calendared nylon shell is very lightweight and has a soft feel, yet seems to be durable and downproof. I looked over the quality of the sewing and other details, and found that it is very well made. 2) SIZING: According to Montbell, the size Long bag will fit users up to 6 feet 4 inches ( cm), and I agree. I am 6 feet tall (183 cm) and there is plenty of length to spare. Montbell specifies that the shoulder area will stretch out to a girth of 64 inches (163 cm). I got into the bag while wearing a down jacket and pants and found the girth ample to accommodate extra clothing. So far I have not noticed any down compression from the bag is too tight. 3) FEATURES: Although this is an ultralight sleeping bag, it still has several useful features. The main features are: full-length zipper with double sliders, down-filled draft collar behind the zipper, hood with drawcord closure, elastic seams that draw the sleeping bag around the body, and a drawcord closure at the foot. The bag does not have an interior pocket or a neck draft collar. 4) INSULATION AND LOFT: To measure the bag's loft I thoroughly shook the bag vertically and horizontally, then laid it on a table for 24 hours to allow the down to fully expand. Then I held a yardstick horizontally over the bag at several locations and measured its double-thickness loft with a ruler. The average double thickness loft was approximately four inches (10 cm). Dividing by two, the single thickness loft is approximately two inches (5 cm). As a rule of thumb, it requires about 2.5 to 3 inches (6 to 7.5 cm) of single layer loft to achieve a comfortable temperature rating of 32 F (0 C). The Montbell Alpine #3 only has two inches (5 cm) of loft, so its temperature rating may be optimistic. I found the bag to be underweight by 0.85 oz (24 g), and that amount of extra down would certainly increase the loft significantly. Also, for an expensive ultralight sleeping bag, 725 fill-power down is low by today's standards. Montbell should consider using at least 800 fill-power down. 5) CONVENIENCE: The horizontal seams have an elastic stitching that causes the bag to hug my body when I am inside. I found it easy to move inside the bag, with the bag easily expanding to accommodate my movements. In my opinion, the stuff sack provided with this bag is too small. It takes a lot of effort to stuff the sleeping bag into the small sack, and then there is a second drawcord to pack it down even smaller! Montbell promotes the compressibility of this bag, so it takes up little space in a backpack. However, I personally feel that too much compression damages the down, and prefer to use a larger stuff sack that the bag easily packs into (however it does take up more space in a pack). The shoulder girth of this bag expands to 64 inches (163 cm), which is very roomy and will allow lots of space to wear additional clothes inside the bag to extend its warmth. The "hugger" feature appears to be a good approach to offer a sleeping bag with plenty of girth to accommodate people of different sizes, yet pull the down close to the user's body for extra warmth. How smooth is the zipper to operate? Does the zipper snag easily? How easy does the hood tighten and loosen? 6) COMFORT/WARMTH: Does the bag meet its 32 F (0 C) temperature rating, i.e., is its rating optimistic or conservative? Is the hood adequately insulated? Does the bag have sufficient draft collars to seal out drafts? Does the shell fabric breathe well, so body moisture is not retained in the bag? Are the zipper and hood draft free? Does the down stay evenly distributed in the baffles, or do cold spots develop? 7) USABILITY AND PERFORMANCE: How well does the bag perform in the field under a variety of sleeping systems and weather conditions? Is the shell fabric adequately down-proof? How does the top/bottom distribution of down effect its warmth? How well do its elastic "hugger" cords improve the bag's warmth by decreasing the volume I have to heat? Is the bag's girth large enough to wear clothing inside the bag to extend its warmth? Is the stuff sack lightweight and the right size for the sleeping bag? 8) WATER RESISTANCE: How well does it shed dew or a light shower? Does the Montbell Alpine Down Hugger #3 Sleeping Bag's DWR treatment eliminate the need to also carry a bag cover or bivy sack when sleeping a poncho/tarp? 9) BREATHABILITY: How breathable is the shell; does it readily allow water vapor to pass through? Under very humid conditions - such as in an extended rainstorm - does the bag's down absorb some moisture? Does the bag readily dry out if it gets damp inside? 10) DURABILITY: Is the bag's shell fabric durable enough for normal backpacking conditions, i.e., does it snag or puncture easily? How does the bag hold up long-term under responsible but constant use? Does the bag lose any loft after repeated use and many stuffings? How does the stuff sack hold up, i.e., no failed seams? 11) SUITABILITY FOR ULTRALIGHT BACKPACKING: the Montbell Ultralight Alpine Down Hugger #3 Sleeping Bag is in the normal weight range for an ultralight 32 F sleeping bag; is its warmth and utility comparable with other bags in the same range? How much can I extend its temperature range? I would like to thank Montbell and the BackpackGearTest Group for selecting me to participate in this test.
[email protected]	Here is my LTR for editing. Thanks in advance. The html version is in the test folder at: http://www.backpackgeartest.org/reviews/test/TESTS/Montbell%20Alpine%20Down%20Hugger%203%20Sleeping%20Bag%20LTR/ Location for Testing: Southwestern US (Colorado, Utah, Arizona, New Mexico). I have been an avid backpacker for 48 years. Backpacking is my passion. In the fall, winter, and spring I backpack in UT, AZ, and NM, and snow camp in the Colorado mountains. In the summer I backpack in several wilderness areas in southern Colorado, and occasionally backpack in the central and northern Rockies. Backpacking Style-I have been a lightweight backpacker for many years and an ultralight backpacker for 7 years. My wife and I give workshops on ultralight backpacking and lightweight food and cooking in our local area, and maintain a website called Southwest Ultralight Backpacking (http://home.bresnan.net/~swultralight) to share information. Photo caption: MontBell Ultralight Alpine Down Hugger #3 Sleeping Bag (photo from MontBell website). The Montbell Ultralight Alpine Down Hugger #3 is a "mixed bag", so to speak. At 21.2 ounces (600 g), it is definitely light for a 32 F (0 C) rated bag. And that weight includes several useful features, like a full-length zipper, drawcord at the foot, and a well-proportioned hood. Its lightweight Ballistic Airlight shell fabric is soft, downproof, and very water-resistant. However, the bag has only 2 in (5 cm) of single layer loft and is chilly to sleep in when the temperature drops to near its temperature rating. In my opinion, the bag needs a little more down or higher lofting down, to bring it to its claimed temperature rating. The Montbell Alpine series is their lightest and most compressible sleeping bags. The Ultralight Alpine Down Hugger #3 is a down-filled sleeping bag rated at 32 F (0 C). Its features are as follows (information taken from the Montbell website): 725 fill power goose down is hypoallergenic and resistant to moisture. Shell and lining are 15x24 denier Ballistic AirlightT hollow fiber calendared nylon with DWR treatment on the outside. Vertical baffles maintain the even distribution of down while allowing the down to loft completely. Gathered Quilt System draws the insulation closer to the body and keeps heat in the bag. Full length zipper for easy entry and double sliders for temperature regulation. Draft tube prevents cold air from entering the bag through the zipper. Double compression stuff sack allows the bag to be compressed to a very small size. Bottom Adjustor System is a drawcord at the foot that allows the length of the bag to be adjusted to the user's height, and allows the user to create a "bootie" around the feet for extra warmth. ** Cotton bag provided for longer-term storage TEST PERIOD-Mid-April to September 2006. TEST LOCATION-Southwestern US (Colorado, Utah, New Mexico, and Arizona). TESTING CONDITIONS-The testing environments consisted of: canyon country, forests, and alpine terrains. Elevations ranged from 5000 to 12,500 feet (1524 to 3810 m). Extreme conditions included: strong winds, dust/rain storms, heavy rain, low temperatures, and high elevations with intense thunderstorms. I tested the bag at temperatures both above and below its temperature rating, and in wet and dry conditions. ACTIVITIES-The Montbell Ultralight Alpine Down Hugger #3 Sleeping Bag was tested while backpacking. USE TO DATE-During four months of testing I have used the Montbell Ultralight Alpine Down Hugger #3 Sleeping Bag on 14 backpacking trips totaling 42 days (28 nights) and two car camping trips totaling 4 days (2 nights). Nighttime temperatures ranged from 22 to 65 F (-5.6 to 36 C). The shelters I slept in were a single-wall tent, a poncho-tarp, and a double-wall tent. Photo caption: The Montbell Ultralight Alpine Down Hugger #3 Sleeping Bag was mainly used as part of an ultralight backpacking system including a plastic groundsheet, torso-length sleeping pad, and poncho-tarp type shelter (Six Moon Designs Gatewood Cape). DATA-On each trip I recorded the following data in relation to my comfort sleeping in the Montbell Alpine Down Hugger #3 Sleeping Bag: 1) temperature in my shelter and outside, 2) estimated wind speed, 3) estimated humidity, 4) altitude, 5) precipitation (including what form), 6) sleeping system the Montbell Ultralight Alpine Down Hugger #3 Sleeping Bag was used in, 7) clothing worn inside the bag, and 8) how well it performed in terms of warmth, utility, and comfort. My four-month evaluation of the Montbell Ultralight Alpine Down Hugger #3 Sleeping Bag is broken down into ten specific factors. 1) MATERIALS, QUALITY, AND CONSTRUCTION: The Ballistic AirlightT hollow fiber calendared nylon shell is really impressive. It's very lightweight and has a soft feel, yet is durable and downproof. I looked over the quality of the sewing details, and found that it is very well made. Calendering is a heat treatment that strengthens the nylon fabric (similar to tempering steel), but it also makes it less breathable. 2) SIZING: According to Montbell, the size Long bag will fit users up to 6 feet 4 inches (193 cm), and I agree. I am 6 feet tall (183 cm) and there is plenty of length to spare. Montbell specifies that the shoulder area will stretch out to a girth of 64 inches (163 cm). I slept in the bag while wearing either a down jacket or a synthetic jacket and found the girth ample to accommodate extra clothing. I did not experience any down compression from the bag being too tight. 3) FEATURES: Although this is an ultralight sleeping bag, it still has several useful features: full-length zipper with double sliders, down-filled draft collar behind the zipper, hood with drawcord closure, elastic seams that draw the sleeping bag around the body, and a drawcord closure at the foot. The bag does not have an interior pocket or a neck draft collar. 4) USABILITY: The horizontal seams have an elastic stitching that causes the bag to contract and hug my body when I am inside. The bag easily expanded to accommodate my movements inside the bag, and it did not inhibit my movements in any way. In my opinion, the stuff sack provided with this bag is too small. It takes a lot of effort to stuff the sleeping bag into such a small sack, and then there is a second drawcord provided to compress it down even smaller! Montbell promotes the compressibility of this bag so it takes up little space in a backpack. However, I personally feel that too much compression damages the down. After using the provided stuff sack a few times, I refused to use it any longer for fear of damaging the sleeping bag. Henceforth I used a larger stuff sack that the bag more easily packed into (however it did take up more space in my backpack). The shoulder girth of this bag expands to 64 inches (163 cm), which is very roomy and provided lots of space to wear additional clothes inside the bag to extend its warmth. The "hugger" feature appears to be a good approach to offer a sleeping bag with plenty of girth to accommodate people of different sizes, yet pull the down close to the user's body for extra warmth. The full-length zipper operates fairly smoothly for getting in and out of the bag. It easily snags on the shell fabric (especially on some labels midway), but no more than other ultralight bags I have used. There is a small Velcro tab at the top of the zipper to keep the zipper from opening from my body movements. However, I found on many occasions (especially when wearing an insulated jacket inside the bag) that the tab does not hold and the zipper opened when I turned over. It helped to squeeze the tab to make the Velcro grip better. I personally feel that a full-length zipper is overkill on an ultralight sleeping bag. For my backpacking conditions (western mountain and desert camping, usually in cool weather) I would be perfectly happy with a half-length zipper or no zipper. However, on one warmer 65 F (36 C) night I completely unzipped the sleeping bag and used it as a quilt. The hood is ample sized and covers my face down to my mouth when drawn, so it kept my face warm. There is plenty of room inside to accommodate wearing a warm hat. The drawcord does not operate as smoothly as I would like. I suggest using a slightly smaller diameter and smoother cord for the mini-cordlock that is used. 5) INSULATION AND LOFT: When the bag was new I measured its loft by thoroughly shaking the bag vertically and horizontally, then laying it on a table for 24 hours to allow the down to fully expand. Then I held a yardstick horizontally over the bag at several locations and measured its double-thickness loft with a ruler. The average double thickness loft was approximately four inches (10 cm). Dividing by two, the single thickness loft was approximately two inches (5 cm). I repeated the loft measurement (using the same procedure) at the end of the four-month test to see if the bag's loft had changed from my use. I could not detect any change in loft. With only 10.6 ounces/301 g of down (for size Long) and two inches (5 cm) of loft, in my opinion, the temperature rating of this bag is somewhat optimistic. The bag has vertical baffles to hold the down in place, so it does not have any capability to re-distribute the down (as with continuous baffles) to increase the loft on top. When I held the bag up in front of a strong light I discovered that several compartments (especially in the torso area) contained very little down. In my opinion, this bag would benefit significantly from the addition of another ounce (28 g) of down, or higher lofting down. For an expensive ultralight sleeping bag, 725 fill-power down is low by today's standards. Montbell plans to upgrade to 800-fill power down in their sleeping bags in 2007, however it is uncertain if the amount (weight) of down in the bag will remain the same. When I weighed the bag, I found it to be 0.85 oz (24 g) lower than specified, and reported in my Initial Report that it was underweight. I subsequently figured out that the stuff sack weighs exactly 0.85 ounces (24 g), so I conclude that the manufacturer's specified weight is the weight of the bag plus the stuff sack. 6) COMFORT/WARMTH: In the field, I slept in the Montbell Ultralight Alpine Down Hugger #3 on 16 backpacking and car camping trips, for a total of 45 days and 30 nights. Temperatures ranged from 22 to 65 F (-5.6 to 36 C), with four nights (22, 28, 29, and 30 F/-5.6 to -1 C) below the bag's 32 F/0 C temperature rating. While sleeping in a well-ventilated shelter I found the bag to be warm (for me) down to about 38-40 F (3-4 C), while wearing long johns and a warm cap inside the bag. On cooler nights down to freezing I was chilly below about 38 F (3C) and found it necessary to also wear a synthetic insulated jacket and pants inside the bag. On the coldest night I wore a down insulated jacket and pants inside the bag to stay warm. I am generally a warm sleeper, meaning I don't get cold easily. I found the bag seals up very well to trap heat, and did not detect any drafts around the zipper or hood. The thinly insulated areas in the torso area contributed to an overall chilly feeling when the temperature dropped below 38-40 F (3-4 C). From my experience over four months of use, I conclude that the Montbell Ultralight Alpine Down Hugger #3's minimum comfortable temperature (for me) is around 40 F (4 C), and that the bag is overrated by about 8 degrees F (4 degrees C). However, as I noted above, because of the bag's roominess, it is easy to wear additional insulated clothing inside the bag to extend its warmth down to about 25 F (-4 C) or so. 7) WATER RESISTANCE: The bag's shell fabric has a Durable Water Repellent (DWR) treatment that really repels water. I put some water in a small depression on the bag and let it stand for an hour and it did not soak through. However, the seams are not seam sealed, so water will soak through the stitching. On several backpacking trips, it rained in the evening, then cleared overnight allowing the temperature to drop to freezing (32 F/0 C) or below. I had lots of frost on the outside and inside of my shelter (especially the single wall tent and poncho-tarp), and the Montbell bag was quite damp on the outside. One another occasion I slept in a tent that leaked badly during a rainstorm, which resulted in puddles of water in the tent and on the bag. On another occasion a nighttime thunderstorm blew rain in from the open side of my Gatewood Cape. The rain hit the backside of the sleeping bag and drained down on my sleeping pad. In the morning I was sleeping in a puddle of water. In all cases the bag's surface DWR treatment did a superb job of keeping the moisture from soaking into the bag. The bag retained its loft and I stayed warm. 8) BREATHABILITY: In spite of its calendaring, the shell fabric appears to be adequately breathable to allow moisture to pass out of the bag in response to the thermal gradient created from my body heat. I did not detect any tendency for the bag to accumulate moisture under high humidity conditions. However, periods of wet weather were followed by periods of dry weather, so there were ample opportunities for the bag to dry out. 9) DURABILITY: I found the bag's shell fabric to be adequately durable for normal backpacking conditions, with no snags or punctures whatsoever. I have repeatedly stuffed the bag in a stuff sack and its loft springs back to original proportions each time. The shell fabric is also very downproof; I had very few instances of down penetrating the shell. 10) SUITABILITY FOR ULTRALIGHT BACKPACKING: The Montbell Ultralight Alpine Down Hugger #3 at 21.2 oz (600 g) is definitely compatible with ultralight backpacking. It is roomy enough to wear additional clothing inside to extend its warmth. However, I would readily give up the full-length zipper in exchange for an extra ounce of down. Also, I would prefer a higher grade of down (800 fill power) for a high-end ultralight sleeping bag. I would like to thank Montbell and the BackpackGearTest Group for selecting me to participate in this test.
[email protected]	Hi Larry. "Hi Rick-"; you have the wrong monitor, its Will not Rick. I have only edit for you, and your html version looks good, nice photos. I'm concerned that you have used the cookset in the field on only one day hike, but I note that you intend to use it a lot in the next two months. Go ahead and upload when ready, and be sure to delete your report in the Test folder. Thanks, and happy testing. Will Rietveld, Test Monitor. To get some additional cooking experience with the set, I have also done some cooking at home with them, both on a stovetop and on my camping stove. EDIT: ., I have also done some cooking at home with it. (needs to agree with "set". I suggest saying "cookset" instead of "set".
[email protected]	Hi Rick. This seems like a great concept, if they can overcome the breakdown problems. I have only one edit, go ahead and upload when ready, and be sure to delete your report in the Test folder. Will Rietveld, Test Monitor. I first suspected it was due to the snowmelt source water, which I allowed it to warm, but while the mÜV would begin its cycle it noticeably dim within a few seconds, winking out completely after perhaps half a minute.
[email protected]	Hi Pam. Good thorough report, and your photos really help the reader see what the product looks like. I have just 3 small edits. Go ahead and upload when ready. Thanks, Will. I had originally planned to also use my top burning homemade beverage can stove, but haven't done so yet due to needing to buy or make a stove support for it. COMMENT: It's not really a "stove support", rather it's commonly called a "pot support". The inner raised rim of the primer pan fits the AntiGravityGear stove's concave bottom and holds in securely in place. EDIT: ".holds it securely in place."
[email protected]	Please consider my application to test the OR Zenith Glove. I have read the Survival Guide and Bylaws v. 0609 (especially Chapter 5 & 6 which focus on test and report requirements) and agree to comply with all requirements. My signed Tester Agreement is on file with BGT. I have completed extra owner reviews, and am a BGT monitor. I have participated in 33 BGT tests so far. I am currently testing one item and have applied for the Jetboil Helios test. Thanks for your consideration, and thanks for all the good work you do for BGT. I have been an avid backpacker for 50 years. I am retired and backpacking is my passion. In the fall, winter, and spring I backpack in UT, AZ, and NM. In the summer I backpack in several wilderness areas in southern Colorado. Backpacking Style-I have been a lightweight backpacker for many years and an ultralight backpacker for 9 years. My wife and I give presentations on ultralight backpacking in the local area, and have developed a website called Southwest Ultralight Backpacking (http://home.bresnan.net/~swultralight) to share information. I have participated in 33 BGT tests so far and am very enthusiastic about the Group. I use the items I am testing on numerous trips (28 multi-day trips so far this year, plus many day trips), my evaluations are thorough, and my reports are always well written and on time. To view examples of my work, see my recent reports (URL's at the bottom of my application). If I am selected to participate in this test, I can assure you that the OR Zenith Glove will receive a lot of testing. TEST LOCATIONS-Southwestern US (CO, AZ, UT, NM). The test will run approximately Dec - Mar. This is perfect timing because I can test the OR Zenith Glove in a variety of activities, environments, and conditions. The testing environments and conditions will consist of: high elevation alpine country, desert, canyon country, and forests. Expected extreme conditions include: rain, strong winds, snow storms, low temperatures, and high elevations. Elevations will range from 5,000 to 12,500 feet and temperatures will range from subzero to 50 F. The OR Zenith Glove will be tested doing the following activities: 1) late fall and winter car camping, 2) winter snow camping, 3) backcountry skiing and snowshoeing, and 4) ice fishing. In late fall and winter, I will be winter car camping in remote southern Utah backcountry, and will wear the gloves on cold evenings and mornings. Snow camping will be in an igloo hut system my wife and I will construct each winter. I will use the Zenith glove a lot for day and overnight backcountry skiing and snowshoeing trips. Finally, the Zenith glove will provide needed dexterity (over mitts) for ice fishing in very cold temperatures. AMOUNT OF USE-I am retired and live in an area surrounded by millions of acres of public lands. I go on outdoor trips every week, often several times a week. The Zenith gloves will receive a lot of use during the four month test. MEASUREMENTS-On each trip I will record the following data in my log book so I have accurate records: 1) temperatures, 2) wind speed, 3) humidity, 4) altitude, 5) activity, 6) how the OR Zenith Glove was used, and 7) how well it performed in different conditions. FACTORS EVALUATED-Specific factors I will be evaluating the OR Zenith Glove for are as follows: 1) CONSTRUCTION, QUALITY, AND FIT-Are construction and workmanship good? Do they fit well (tightness/looseness, length)? 2) PERFORMANCE (COMFORT)-How does the lining feel against my skin? Do they readily wick moisture away from my skin and dry quickly? How comfortable are they at different exertion levels? Do they have a broad comfort range? 3) PERFORMANCE (WARMTH)- How warm are they? How warm are they in various cold weather activities and exertion levels-like snowshoeing, ice fishing, winter camping, and winter hiking? Can I layer gloves inside them or wear gloves of different types in them to produce a versatile hand warming system? 4) PERFORMANCE (WATER-RESISTANCE)-How well do they resist getting wet in rainy or snowy weather? Do they dry out quickly if they do get wet? A really good test of waterproofness for gloves is igloo building, especially with wet snow, because the gloves are used to pack snow in a form for several hours. 5) PERFORMANCE (ARTICULATION/DEXTERITY)-How much can I move my hands inside the gloves? How much dexterity do I have with the gloves on - can I pick up things, change outer clothes, or get into my pack with the gloves on, or do I have to take them off? Does the AlpenGrip surface grip things well, like ski poles or snowshoes? 6) DURABILITY-How durable are the Zenith Gloves? Are they adequately reinforced in wear zones? I wear out gloves rather quickly while bushwhacking; how well do the Zenith Gloves stand up to handling rock and brush? What is their life span likely to be under the conditions I am using them? How durable are the liner gloves? 7) VERSATILITY-What is its versatility for different outdoor activities? How much layering can I do with these gloves, ie wearing two or more liners inside or wearing a heavier glove inside than the one that comes with the Zenith? If the liner gloves wear out, can I readily replace them with other gloves? 1) Western Mountaineering Highlite Sleeping Bag 2) Safewater Anywhere Personal Water Filter 3) GoLite Breeze Pack 4) Oware 8x10 Flat Silnylon Tarp 1) Montbell Ex Light Down Jacket http://www.backpackgeartest.org/reviews/Clothing/Jackets/MontBell%20EX%20Lite%20Down%20Jacket/Test%20Report%20by%20Will%20Rietveld/ 1) SealSkinz Gloves and Socks 2) GoLite Trek Backpack 3) Tarptent Squall 4) Brasslite Turbo II-D Alcohol Stove 5) Hot Chillys Bio-Silver Bi-Ply Baselayer 6) Therm-a-Rest Prolite 3 Short Sleeping Pad 9) Ex Officio Buzz Off Lite LS Shirt 10) Ex Officio Buzz Off Convertible Pant 11) Equinox Rainsuit 12) Ibex Guide Lite Pant 13) ULA Fusion Pack 14) Dunham Waffle Stomper Terrastryder Mid-Height Boot 15) Ibex Scull Cap 16) Integral Designs eVENT Rain Pant 17) Integral Designs eVENT Shortie Gaiters 18) Spenco Backpacker Footbeds 19) Teko Socks 20) Ibex Scout ½ Zip Shirt 21) OR Talon Gloves 22) Duofold Varitherm Silkweight Baselayers 23) Montbell Alpine Down Hugger #3 Sleeping Bag 24) National Geographic State TOPO Software 25) Xyflex Thermals 26) Black Diamond Cosmo Headlamp 27) Montbell Alpine Light Down Pant 28) Bushnell ONIX 200CR GPS 29) GoLite Diablo Parka 30) Hot Chillys Chamois Zip T 31) GoLite Adrenaline 20 Sleeping Bag http://www.backpackgeartest.org/reviews/Sleep%20Gear/Sleeping%20Bags/GoLite%20Adrenaline%2020%20Sleeping%20Bag/Test%20Report%20by%20Will%20Rietveld/ 32) Integral Designs Penguin Reflexion Bivy http://www.backpackgeartest.org/reviews/Shelters/Tarps%20and%20Bivys/Integral%20Designs%20Penguin%20Bivy/Test%20Report%20by%20Will%20Rietveld/ 1) Nite Ize Biners and Figure 9s 2) Buff Cyclone Hat
[email protected]	Hi Kurt. Excellent report and great photos! I have only a few small edits for you. Go ahead and upload when ready, and be sure to delete your report in the Test folder. Thanks! Will Rietveld, Test Monitor. My principle use of the small Figure 9s was to tie down my tarp guy lines for my hammock to the stakes. EDIT: principal Observations: one of the things I noticed was the the Figure 9's are not easy to slide up and down on a rope in the fixed end configuration, particularly when wearing gloves in cold weather. EDIT: delete second "the" I could not just pull on the loose rope and and slide it up or down. EDIT: delete second "and" Once again the small Figure 9's did their typical great job of tyeing down my hammock tarp.
[email protected]	Hi Leesa, I just have a few smaller edits. The html version looks fine. Be sure to check hyperlinks when you upload, and delete your review in the Test folder. Thanks. Will. EDIT: In your spec table, Shoulder I have been able to use the Glow Sleeping bag of 13 occasions during the last two months. EDIT: on 13 occasions Although this bag is rated at 15 F (-9 C), I found it useful even in the summer, here in northern New England. EDIT: Extra space after (-9C), Its nice to wake up in the morning, still on the sleeping pad. EDIT: It's
[email protected]	Hi Jo Ann. Thanks for the edits. I have revised my IR and uploaded it to its folder. Best, Will. Thank you for your review! Just a few edits and you can upload to the appropriate folder here: http://snipurl.com/20uqj See you in a couple of months! Edit: The body of your HTML contains at least two different fonts. If this was intentional ok, but it would look more consistent if it was all in one font. EDIT: Your entire Product Description is copied directly from the manufacturer's website. The information from the website can easily be obtained by our readers by navigating to the manufacturer's page.The portion where you have the Features listed in a bulleted format is fine, but the rest of it will have to be put into your own words from your experience with viewing the item in your hands. Please and thank you. EDIT: As well here, the information you have on the SympaTex excerpt from Wikipedia reads well, like an encyclopedia. :) Very little of the Initial Impressions section is actually your impressions. It is ok to use Wiki to research the information, but please minimize the information you are quoting directly from their website. EDIT: 'Long' need not be capitalized as it is not the beginning of a sentence, a pronoun, place, title, noun, or name. You have two instances of this in the paragraph above. EDIT: You need punctuation at the end of this paragraph. A colon would be most suitable.
[email protected]	Hi Karl. Thanks for posting your revised FR. However, BGT policy is for the tester to upload the html version to the Test folder and provide a link to it in a post here for the convenience of the test monitor (see the BGT Bylaws and Shane's recent reminder). Please upload your html version (as I requested before) then repost your FR. I will be happy to look at it again when its ready. Thanks. Will
[email protected]	Please consider my application to test the Gramicci Flash Tech Henley and Long Johns. If selected, I would need a men's size Large, color Stone. I have read the new BGT Bylaws v. 0609, and have a signed Tester Agreement on file. I agree to follow all BGT tester requirements. I have completed extra owner reviews, and am a BGT monitor and mentor. I have participated in 27 BGT tests so far, and I am testing one item right now. Thanks for your consideration, and thanks for all the good work you do for BGT. I have been an avid backpacker for 48 years. I am retired and backpacking is my passion. In the fall, winter, and spring I backpack in UT, AZ, and NM. In the summer I backpack in several wilderness areas in southern Colorado. Backpacking Style-I have been a lightweight backpacker for many years and an ultralight backpacker for 7 years. My wife and I give presentations on ultralight backpacking in the local area, and have developed a website called Southwest Ultralight Backpacking (http://home.bresnan.net/~swultralight) to share information. I have participated in 27 BGT tests so far and am very enthusiastic about the Group. I am retired, in good physical condition, and I get out several times a week. I use the items I am testing on numerous trips, my evaluations are thorough, and my reports are always well written and on time. To view examples of my work, see my recent reports (URL's at the bottom of my application). If I am selected to participate in this test, I can assure you that the Gramicci Flash Tech Henley and Long Johns will receive a lot of testing. Specifically, testing will be done: Every week, usually several times a week. (I'm retired, and get out a lot.) In the Southwestern US In alpine, forest, canyon, and desert environments. Under cold, wet, dry, humid, and windy conditions. ** In a variety of outdoor activities. TEST LOCATIONS-Southwestern US (CO, AZ, UT, NM). The test will run approximately mid-Nov to mid-Feb. This is perfect timing because I can test the Gramicci Flash Tech Henley and Long Johns in a variety of activities, environments, and conditions. The testing environments and conditions will consist of: high elevation alpine country, desert, canyon country, and forests. Expected extreme conditions include: rain, strong winds, snow storms, low temperatures, and high elevations. Elevations will range from 5,000 to 12,500 feet and temperatures will range from subzero to 60 F. I know the emphasis in BGT is backpacking, but long johns are suited for a variety of activities, and it is more difficult to backpack in the wintertime. The Gramicci Flash Tech Henley and Long Johns will be tested doing the following activities: 1) backpacking, 2) backcountry winter car camping, 3) snow camping, 4) cold weather day hiking, 5) snowshoeing, 6) backcountry skiing, and 7) ice fishing. I will be going on several backpacking trips in southern Utah, and Arizona in late fall. This winter I will be winter car camping and day hiking in the southern Utah backcountry. Snow camping will be in an igloo hut system my wife and I will construct this winter. Once we have a good snowpack in the mountains I will be snowshoeing or backcountry skiing every week, often staying out overnight. Also, starting around December 15, I will go ice fishing weekly with my brother. AMOUNT OF USE-I am retired and live in an area surrounded by millions of acres of public lands. I get out several times a week. On my previous tests, I used the gear about 40 days during the four month test period. From the time the Gramicci Flash Tech Henley and Long Johns arrive, they will go with me every time I go out, which averages 2-3 days a week. MEASUREMENTS AND DATA-On each trip I will record the following data using a Kestrel 4000 Pocket Weather Meter and take notes in my log book so I have accurate records: 1) weather conditions: precipitation (type and amount), temperature, wind speed, relative humidity, dewpoint, and wind chill; 2) altitude, 3) activity, 4) how the Gramicci Flash Tech Henley and Long Johns were worn (clothing system), 5) my comfort level wearing the baselayers, and 6) how well the baselayers worked in different activities. FACTORS EVALUATED-The specific factors I will be evaluating the Gramicci Flash Tech Henley and Long Johns for are as follows: 1) CONSTRUCTION, QUALITY, AND FIT-Are construction and workmanship good? Do they fit well (tightness/looseness, sleeve length, body length, leg length) Are they non-binding? 2) PERFORMANCE AS A BASE LAYER-How do they feel against my skin? Do they readily wick moisture away from my skin and dry quickly? Do they hold body heat well? If I wear them while hiking, how comfortable are they at different exertion levels? Do they have a broad comfort range? Are they sufficiently warm (or too hot) for cool/cold weather hiking? Are they comfortable over a wide temperature range, e.g. days that start out below freezing and warm up into the 50's or 60's? 3) PERFORMANCE IN COMBINATION WITH OTHER PERFORMANCE CLOTHING-For example, how well do they perform in rainy weather and moderate to high exertion? How comfortable are they to wear with various outside layers in cold weather activities-like winter backpacking, snow camping, snowshoeing in the alpine country, and ice fishing? Does other clothing slip over them easily? 4) PERFORMANCE IN A SLEEPING SYSTEM-Do the Gramicci Flash Tech Henley and Long Johns provide a lot of warmth for their weight when worn in a sleeping bag to extend its warmth? 5) ODOR MANAGEMENT-How effectively do they restrain or eliminate odors? Does washing completely remove odors? 6) DURABILITY-How durable are the Gramicci Flash Tech Henley and Long Johns? Does the material pill in wear zones? What is its life span likely to be under the conditions I am using them? 7) VERSATILITY-What is their versatility for different outdoor activities? In my evaluation, I will assess their utility for various uses, including ultralight backpacking. 9) CLEANING-How easily and well does the Gramicci Flash Tech Henley and Long Johns clean following the label instructions? 10) SUITABILITY FOR ULTRALIGHT BACKPACKING-How does the Gramicci Flash Tech Henley and Long Johns compare with similar products as far as warmth and weight? 1) Western Mountaineering Highlite Sleeping Bag 2) Safewater Anywhere Personal Water Filter 3) GoLite Breeze Pack 4) Oware 8x10 Flat Silnylon Tarp 1) Montbell Light Alpine Down Jacket (item received, will write IR soon) 1) SealSkinz Gloves and Socks 2) GoLite Trek Backpack 3) Tarptent Squall 4) Brasslite Turbo II-D Alcohol Stove 5) Hot Chillys Bio-Silver Bi-Ply Baselayer 6) Therm-a-Rest Prolite 3 Short Sleeping Pad 9) Ex Officio Buzz Off Lite LS Shirt 10) Ex Officio Buzz Off Convertible Pant 11) Equinox Rainsuit 12) Ibex Guide Lite Pant 13) ULA Fusion Pack 14) Dunham Waffle Stomper Terrastryder Mid-Height Boot 15) Ibex Scull Cap 16) Integral Designs eVENT Rain Jacket 17) Integral Designs eVENT Shortie Gaiters 18) Spenco Backpacker Footbeds 19) Teko Socks 20) Ibex Scout ½ Zip Shirt 21) OR Talon Gloves 22) Duofold Varitherm Silkweight Baselayers 23) Montbell Alpine Down Hugger #3 Sleeping Bag 24) National Geographic State TOPO Software http://www.backpackgeartest.org/reviews/Software/Topographic%20Mapping/National%20Geographic%20TOPO%20State%202006/Will%20Rietveld/Long%20Term%20Report/ 25) Xyflex Thermals http://www.backpackgeartest.org/reviews/Clothing/Underwear/Zyflex%20Thermal%20Shirt%20and%20Pants/Will%20Rietveld/Long%20Term%20Report/ 26) Black Diamond Cosmo Headlamp http://www.backpackgeartest.org/reviews/Lighting/Headlamps%20-%20LED/Black%20Diamond%20Cosmo/Will%20Rietveld/Long%20Term%20Report/ 1) Princeton Tec Quad Headlamp One person-helping him complete his OR's
[email protected]	Hi Richard. Lots of testing and a thorough report, just what we like to see. Great photo! I have only a couple of edits for you. Go ahead and upload when ready, and be sure to delete your report in the Test folder. Thanks! Will Rietveld, Test Monitor. Temperatures from 50-85 F (10-29 C), with one brief rain shower but no sustained precipitation and low humidity. EDIT: Not a complete sentence; suggest: Temperatures ranged from. A small price to pay for a highly functional pair of sunglasses, however. EDIT: Not a complete sentence; suggest: That's a small price to pay.
[email protected]	Hi Tim. Here are your edits. Another test done. Go ahead and upload. How's your mom doing? Will Parkview 2 EDIT: I recommend putting the word "Tent" in the title. 4 lb 6 oz (2.0 kg) - Fast Fly weight Comment: This is the first of 15 uses of the term "Fast Fly". In 10 of the uses you have them capitalized and in 5 you don't (3 under Measured Weight and 2 in the first paragraph under My Thoughts on the Parkview). For consistency, you might want to make them all capitalized. Although many of the places I hike in the warm weather are bug infested. EDIT: This is a sentence fragment. You could delete the "Although" at the beginning to make it a standalone sentence. The rain fly (aka Fast Fly) was really too much protection for me in the summer months. Comment: I like how you equated Fast Fly with rain fly, but suggest that instead of doing here, put in (aka rain fly) after the first use of the words Fast Fly (under Published Weight). It's is in this versatility that I found the Parkview really shined. EDIT: Delete either "..'s" or "is". As I mentioned in my Field Report, I extended the size of the footprint by adding Tyvec to cover the areas defined by the vestibules in the Fast Fly mode, and in essence transformed the Parkview into a three-man tent. EDITS: Change "Tyvec" to "Tyvek". Also, I recommend "three-person" instead of "three-man". I would like to see it shortened up a bit so the whole package took on a more rigid shape. EDIT: Change "took" to "takes". It's roominess. Edit: Change "It's" to "Its" The Parkview II is a great tent. EDIT: BA lists it as the "Parkview 2" on their website, and you list it that way in your title and introduction.
[email protected]	Hi Sam. Good test and report. I have a few edits and one comment on your LTR. Go ahead and upload when ready, and be sure to delete your report in the Test folder. Thanks! Will Rietveld, Test Monitor. I found the Buff make comfortable to wear and easy to take on and off. EDIT: I believe "make" should be "very". During the field testing I found that Buff Cyclone to be extremely warm and block the wind very well. EDIT: I believe "that" should be "the" I have stuffed it my pocket and backpack, it has been dropped on the ground many time and even stepped on after it ended up on the floor of my car for a week. EDIT: .stuffed it in my pocket. I used a damp cloth on it to spot clean it until it finally fell into a mud puddle. I put it through the washing machine and it came out looking new and does not show any sign of losing its shape or color. COMMENT: The first sentence is confusing. Perhaps you could re-write this to be more clear.
[email protected]	Hi Rick. The text of your LTR looks good. I hope you can overcome the problems with the Report Writer so your photos come through when you upload to the folder. Your photos in your IR and FR are excellent, and I assume the ones in your LTR are just as good. By far, you have had the most problems with this product, but both the mfr and you remain upbeat, so that's a good testament to the value of the product (when debugged). Go ahead and upload to the folder when ready, and be sure to delete your report in the Test folder. Thanks! Will Rietveld, Test Monitor.
[email protected]	Hi Leesa. I have several edits and comments for you to consider. Html version looks good. Go ahead and upload when ready. Thanks! Will Rietveld, Test Monitor. January 8, 2008 Over the last two months, I used the cookset on 2 - two night trips and three day trips. SUGGESTION: This is a little confusing. How about ".I used the cookset on two 3-day trips (2 nights) and three 1-day trips." The weather had turned much colder with night time temperatures in the 10 - 15 degree F range (C) and day time temperatures hovering around freezing. EDIT: Need metric equivalent. This was just a minor issue that required me to adjust my planning, but didn't effect the overall quality of the food. EDIT: affect I used it the set to heat both soup and water for hot chocolate. EDIT: I used the set. (delete the extra "it") It shouldn't effect future use - and it doesn't appear like it will spread. EDIT: affect I had reservations in the begining about the handle being sturdy enough to hold the pots if they were full of hot liquid. Thank you to Backpackgeartest.org and Optimus for the opportunity to test this cookset.
[email protected]	Hi Thomas. I have several edits for you. Html version looks good and thanks for including photos. Go ahead and upload when ready, and be sure to delete your report in the Test folder. Thanks! Will Rietveld, Test Monitor. Materials: 100% microfiber polyester, elastic banding, WIndstopper, Polartec 100 microfleece. This was an intriguing idea to me since I could put a multipurpose cold weather head covering to pretty good use. EDIT: Extra space after "I" The Cyclone Buff is a tube of clothe that can be worn in many different configurations. EDIT: cloth The top 12 inches (30 cm) of the Cyclone is made from two layers of Buff Fabric (99% polyester and 1% PTFE) that designed to trap warm air between the layers. The the next section of the Cyclone is made up of 3/4 GORE WINDSTOPPER fabric and another panel of what seems to be elastic fleece which makes up up about 1/4 of this section. EDIT: delete extra "the" and extra "up" All of these materials are assembled into one continuos tube of fabric. EDIT: continuous The Buff Cyclone is much heavier (I did not know exactly what Gore Wind Stopper Fleece was) than I expected and it isn't made up of just one fabric. The combination of Buff fabric, GORE Windstopper, and elastic fleece combines to make what is hopefully a truly multi function piece of gear. EDIT: Gore EDIT: multi-functional
[email protected]	Hi Richard. I have just one comment on your IR and no edits. The html version looks good. Go ahead and upload when ready and be sure to delete your report in the test folder. Thanks! Will Rietveld, Test Monitor. I first used a Tablet on a one-liter Nalgene bottle of tap water to test for discoloration or taste. I popped a pill into this about 11 pm and left the bottle on my kitchen counter. Early the next morning there was no color to the water and no noticeable taste. COMMENT: You should specify the conditions. If you are on a municipal water supply, the tap water probably already has chlorine dioxide in it, so this would not be a good taste test. However, if you live in the country and are using well water, this would be a good taste test.
[email protected]	Please consider my application to test the Tarptent Double Rainbow Tent. If selected I would like to test the Double Rainbow with sewn-in floor. I have read and re-read the BackpackGearTest Survival Guide version 1202, especially Chapter 5, and have a signed Tester Agreement on file. I agree to follow all BGT tester requirements. Thanks for your consideration, and thanks for all the good work you do for BGT. I have been an avid backpacker for 48 years. Backpacking is my passion. In the fall, winter, and spring I backpack in UT, AZ, and NM. In the summer I backpack in several wilderness areas in southern Colorado. Backpacking Style-I have been a lightweight backpacker for many years and an ultralight backpacker for 7 years. My wife and I give presentations on ultralight backpacking in the local area, and have developed a website called Southwest Ultralight Backpacking (http://home.bresnan.net/~swultralight) to share information. I have participated in 26 BGT tests so far and am very enthusiastic about the Group. I use the items I am testing on numerous trips, my evaluations are thorough, and my reports are always well written and on time. To view examples of my work, see my recent reports (URL's at the bottom of my application). If I am selected to participate in this test, I can assure you that the Tarptent Double Rainbow Tent will receive a lot of testing. Specifically: I am retired and backpack nearly every week in the summer and fall. My wife and I backpack and car camp together and will share the tent. My wife is an expert seamstress, and will evaluate the sewing quality I will have friends use the tent and give me their input. Testing will be in the Southwestern US I will test the tent in alpine, forest, canyon, and desert environments. ** I will test the tent under hot, cold, wet, dry, humid, and windy conditions. TEST LOCATIONS-Southwestern US (CO, AZ, UT, NM). The test will run approximately Aug-Nov. This is perfect timing because I can test it in alpine environments in Aug and early September during our monsoon season (intense thunderstorms with lots of wind), then in canyon country during the fall. The testing environments will consist of: high elevation alpine country, badlands desert, canyon country, and forests. Expected extreme conditions include: heavy rain, strong winds, snow storms (in the mountains any time after Sept 15), dust/rain storms, intense sun, low temperatures, and high elevations with strong UV and intense thunderstorms. Elevations will range from 5,000 to 12,500 feet and temperatures will range from 20 to 85 F. Note: During August and early September I will be testing the tent in the alpine zone (above timberline), where it will be exposed to intense thunderstorms with heavy rain and strong winds. Nighttime conditions are usually calm and cool, which are conducive to heavy condensation inside a single-wall tent. The Tarptent Double Rainbow Tent will be tested doing the following activities: 1) backpacking, 2) car camping. TEST PLAN-From the time the Tarptent Double Rainbow Tent arrives, it will be my primary tent every time I go out, which averages one trip a week. On each trip I will record the following data: 1) nighttime temperature, 2) estimated wind speed, 3) estimated humidity, 4) altitude, 5) precipitation (including what form), 6) site where the tent was used, 7) ground surface conditions, and 8) condensation inside the tent. FACTORS EVALUATED-The specific factors I will be evaluating the Tarptent Double Rainbow Tent for are as follows: 1) MATERIALS, QUALITY, AND CONSTRUCTION: Is the tent made of high quality materials, and is it well designed and constructed? 2) SIZING: Is the size adequate for the entries, vestibules, floor, and headroom? How well would this tent work for a tall person? 3) SETUP: How easy is the Double Rainbow to set up compared to other Tarptents and other tents? 4) CONVENIENCE: Is the tent easy to enter? Do the doors secure well? Can the doors be easily secured open when more ventilation is desired? How easy is it to close the vestibules from the inside? 5) USEFUL FEATURES: Is there adequate stowage options (pockets, etc) inside the tent? How useful is the bathtub floor suspended by clips? Can I see outside very well through the top vents? Are there tie loops inside the tent to hang a clothes line? 6) VENTILATION: The tent has what appears to be two small vents at the top of the vestibules. Are the mesh vents at the bottom and the top adequate to get good high/low ventilation when the doors are closed? Is there too much ventilation when its windy? 7) CONDENSATION: Condensation is a fact of life in a single-wall tent. The difference between tents is how well condensation is minimized by good ventilation and fabric porosity. Since the silnylon walls of this tent are not porous, the tent is completely dependent on good ventilation to minimize the condensation issue. So, how well is the Double Rainbow designed to minimize condensation? Does the condensation curtain designed for this tent really work? Under what conditions does condensation occur, and how must the tent be used to avoid or minimize condensation? 8) WIND STABILITY: How secure does the Double Rainbow pitch for wind stability? Are there an adequate number of staking points and guylines to adequately secure the tent in a strong wind? How does the tent do in a strong side wind? (Note: with its monopole design, the Rainbow may be very susceptible to side winds.) 9) STORM RESISTANCE: Does the Double Rainbow stay dry inside during a heavy or prolonged rain, or wind-driven rain? This assumes adequate seam sealing with silicone (all Tarptents need to be seam sealed by the user). 10) BUG PROTECTION: We have lots of mosquitoes and flies at certain locations, which will provide and adequate test of the tent's bug protection. Does the tent completely seal out bugs? 11) DURABILITY: How well does the Double Rainbow hold up under a wide variety of terrains and weather conditions? Are there any weaknesses in the design that need improvement? Is there adequate reinforcement in stress areas? How does the silnylon floor hold up on rough ground? 12) SUITABILITY FOR LIGHTWEIGHT BACKPACKING: The Tarptent Double Rainbow will be one of the lightest 2-person backpacking tents around; how does it compare to similar tents in terms of weight, protected area, features, and ease of use? 1) Western Mountaineering Highlite Sleeping Bag 2) Safewater Anywhere Personal Water Filter 3) GoLite Breeze Pack 4) Oware 8x10 Flat Silnylon Tarp 1) Montbell Alpine Down Hugger #3 Sleeping Bag http://www.backpackgeartest.org/reviews/test/TESTS/IR%20-%20Montbell%20UL%20Alpine%20Down%20Hugger%203%20Sleeping%20Bag/ 2) Xyflex Thermals http://www.backpackgeartest.org/reviews/Clothing/Underwear/Zyflex%20Thermal%20Shirt%20and%20Pants/Will%20Rietveld/Initial%20Report/ 3) National Geographic State TOPO software http://www.backpackgeartest.org/reviews/Software/Topographic%20Mapping/National%20Geographic%20TOPO%20State%202006/Will%20Rietveld/Initial%20Report/ 4) Black Diamond Cosmo Headlamp http://www.backpackgeartest.org/reviews/Lighting/Headlamps%20-%20LED/Black%20Diamond%20Cosmo/Will%20Rietveld/Initial%20Report/ 1) SealSkinz Gloves and Socks 2) GoLite Trek Backpack 3) Tarptent Squall 4) Brasslite Turbo II-D Alcohol Stove 5) Hot Chillys Bio-Silver Bi-Ply Baselayer 6) Therm-a-Rest Prolite 3 Short Sleeping Pad 9) Ex Officio Buzz Off Lite LS Shirt 10) Ex Officio Buzz Off Convertible Pant 11) Equinox Rainsuit 12) Ibex Guide Lite Pant 13) ULA Fusion Pack 14) Dunham Waffle Stomper Terrastryder Mid-Height Boot 15) Ibex Scull Cap 16) Integral Designs eVENT Rain Jacket 17) Integral Designs eVENT Shortie Gaiters 18) Spenco Backpacker Footbeds 19) Teko Socks 20) Ibex Scout ½ Zip Shirt 21) OR Talon Gloves 22) Duofold Varitherm Silkweight Baselayers 1) Black Diamond Enduro Carbon Fiber Trekking Poles 2) Sierra Designs Volt/Glow Tent 3) Rail Riders Extreme Adventure Pants One person-helping him complete his OR's
[email protected]	Hi Andrew. Glad to see you back participating in the group. Your IR is definitely worth waiting for; it looks great, with excellent photos to show the products. I have a few edits for you below. Go ahead and upload when ready, and be sure to delete your report in the Test folder. Thanks! Will The S-Biners and Figure 9's are NOT to be used for climbing or where bodily injury could happen. EDIT: Extra space after "injury" The items I am testing below are two hooks that Nite Ize refer to as figure 9's which will allow me to do away with knots and be able to tie off cords a lot quicker and with a lot more ease. EDIT: refers This means I can clip one end to my pack for example and then be able to clip something else onto the other end EDIT: needs a period at the end of the sentence. The S-Biners are attached to a card which has the size marked on it with the load limit and inside the card a little fold out piece of card showing other products from Nite Ize. EDIT: Run-on sentence. Suggest: The S-Biners are attached to a card which has the size marked on it, along with the load limit. Inside the card a little fold out piece of card shows other products from Nite Ize. I wrapped the cord over the small hook, pulled tight and then around the back and through the serrated v section of the nine. EDIT: 9 instead of "nine", to be consistent The small S-Biner I clipped onto the zipper pull of my bum bag, I use this bag for work every day and so it should get a lot of use during the test period. COMMENT: This might be Aussie talk, but for clarity I suggest the following: I clipped the small S-Biner onto the zipper pull of my bum bag that I use for work every day, so it should get a lot of use during the test period. My measurements below are almost identical (within 2 mm) to the manufactures measurements.
[email protected]	How does the DNS service poller work exactly? Does it try to resolve a given address on the internet? Or just check to see if the port is open? We have a T-1 circuit that is showing a DNS outage but the vendor says the DNS service should be running. They are asking questions on what exactly it tries to resolve and I wasn't sure as to the answer to that question.
[email protected]	We've done RNA-seq on polysome fractionation samples across three different genotypes. We collected Rnp (free mRNA's) and Polysome (actively translating mRNA's) fractions as well as input mRNA from the samples before fractionation. The idea of collecting input is not only so that we can look at transcriptional changes but to normalize to something that would be free of the technical variation and RNA loss that polysome fractionation can produce. This is my current idea for a workflow: Tophat/Bowtie => htseq-count => divide poly/rnp counts by input counts per gene/feature => edgeR differences between genotypes across polysome/rnp/input categories My question is thus: Is there a way to tell edgeR to normalize to the input? Am I mucking things up my manually normalizing the read counts before giving them to edgeR?
Abqnrwb/[email protected]	My install attempt was a litle different: - Installed on a new VM running Windows Server 2008 - Install CSE 1.3 (includes Python 2.5) - Install Genshi 6 I don't have good notes on apache errors, but I do from just trying to run Trac via tracd.exe: log for more information. After that I got a different error: - Warning: Can't synchronize with repository "(default)" (Unsupported log for more information. At that point I gave up and installed BitNami's Trac Stack.
G/[email protected]	I know this is a long message, so I'll summarize my questions here: - Should I release the iterated solution in the same files as their current equivalents or separate them out? - After the iterated solution is done, would you rather see SIMD extensions or a verlet integrator for particles (cloth, water, etc) next? - If SIMD (slightly ahead of the verlet integrator in my mind), then what's the best way to get cross-platform/compiler assembly into the project? - Plus a few internals questions below. And now the long version..... I'm not sure how close what I came up with is to PP, but it's working great! I switched over to LDLT and got immediate improvements from just that switch, I'm guessing because of all the loop unrolling and not having to do Sqrt's. Then I clamped x's that are outside of lo and hi (calculated dynamically if findex > -1), remove their rows and columns from A with a slightly modified dRemoveLDLT (A didn't use row pointers), update rhs, and resolve until no more constraints go out of range (usually only once), and voila! a 150% speed increase over dSolveLCP (and should give the exact same results 95% of the time). I know this algorithm will most likely slow to a crawl with larger systems where it may have to resolve several times, but it works great when it doesn't, and since I'm doing only one joint at a time, it will usually be either impossible or really weird to do more than one resolve. One thing I need to do is change the contact joint so the hard contact constraint is at the end of J instead of the beginning, since it seems more likely that a contact would be limiting penetration rather than friction, and limits at the end are a lot easier to remove than limits at the beginning. Would this do anything to mess up the current algorithm? Now the major bottleneck (takes 4 times as long as any other operation) is computing A. I did find an optimization for that, but I was surprised it wasn't already implemented, since it would help the old version too. So I wanted to ask about it to see if I should make this a change to the original function or make a new one. Here it is: Correct me if I'm wrong, but I believe A is always symmetric (as well as positive definite). This means that A's top right triangle mirrors it's lower left, and possibly (I don't know about this one) every block has mirrored top and bottom triangles...? However, in the step where A is calculated (JinvM * J') a call is made to Multiply2_p8r for each block. Multiply2_p8r calculates every entry in the block, top and bottom half, separately. Shouldn't it calculate the top half and copy the results to the bottom half as it goes (or when it's done)? I know that would work for the diagonal blocks in the current matrix, but I'm not sure about the others. Should I change the current function, or write another version that exploits the symmetry, and change the current algorithm to use that one for the diagonal? The real question is whether every block in A is symmetric or only the ones along the diagonal. Another question: how do you want this integrated into ODE? Right now I have it integrated into the current source files, so you just replace 4 or 5 files and you can start calling dWorldStepFast(world, stepsize, iterations). I've made a few changes to the body class, to store it's inertial tensor and Mass matrix in the global frame. That way I don't have to recalculate it for each joint that is connected to it, only once each iteration. So that file will have to be replaced (or at least those 2 lines). Other than that, I can take the rest of the code out and put it in separate files (and figure out where to change the makefile) if you'd rather it be separated. Just let me know. I guess my next bought of hacking will be SIMD :) What's the most cross-platform/compiler way to get assembly into the project? I guess I could just write it once for gcc inline and once for vc++ inline, but that leaves out the compilers I don't have or care to learn. So what does that leave, GAS and NASM? Anyone have a preference (I'll have to learn either one.... which is "best")? Then I could do a verlet integrator.... anybody interested in cloth and other particle effects (seen some cool water demos)? There's only two constraints: distance (also known as stick constraints) and the angle between 2 sticks. It shouldn't be too difficult to implement them as inequality constraints. The integrator and the collision detection are really integrated, so a simloop would call normal collision and step routines, then the particle engine, and the particles would "flow" around the rest of the bodies. There's a paper on the Hitman game and an article on Gammasutra that explain the concept better, I'll find the links if you're interested. The basic concept is that you just make a particle at each of the vertices of a mesh, and then the mesh would act like cloth and drape over anything it came in contact with, or you could make it weightless and move one particle up and down to make a rippling water effect. You could attach particles to a point on a rigid body. The hard part is going to be getting the rigid bodies to interact with the particles (i.e. if you have a couple boxes sitting on a table cloth, they should move with it if you start dragging the cloth around). The algorithm itself is an iterated one, but the less general constraints make the computations required to integrate a step much faster. So which do y'all want first, more optimization or more functionality?
G/[email protected]	I posted some documentation on the StepFast1 algorithm on my website at http://www.csworkbench.com/stepfast-doc.html . All constructive criticism is welcomed. Let me know if you want more or less explanation, graphics, or anything. Hmmm, I should probably say a little more about the stepsize/iterations/autodisablethreshold relationship. Russ, I came up with just post-fixing SF1 on the stepfast-1 specific functions.... it's a few characters shorter anyway. Let me know if that will/won't work.
G/[email protected]	The transformed geom stores it's positional and rotational offset from the geomTransform. So you have to get position and orientation of the geomTransform, rotate the position of the transformed geom by the orientation of the geomTransform and add this position to the geomTransforms position to get the transformed geom's actual position. You also need to rotate the transformed geom's orientation by the geomTransform's orientation to get the transformed geom's actual orientation. But you're in luck, the code to do all that is in the simLoop function of test_boxstack. I don't have the code right in front of me right now, but it should be in the section that starts with something like "if (cls == dGeomTransformClass)". Ah, but if you hit reply all, I get two copies anyway... but that's
G/[email protected]	You have 2 choices here. For the general case, there's the tri-collider in the contrib directory. It uses OPCODE to do the collision and then converts it's output to ODE contacts. Then, and this would probably work better for your app, there's a heightfield collider in the works. I'm not sure what the status is on that project. Also, there was a dxTriangle class released recently, but it seems like it was more of a tutorial or reference on implementing your own collision class, which is yet another option. Finally, you don't have to use ODE's collision system at all. The collision system in ODE is actually a completely separate entity that exists for the sole purpose of filling in contact joints before every timestep. If you want to fill in your own contact joints without ever calling dCollide, that is completely up to you.
G/[email protected]	Not sure about this one. Set the dContactApprox1 flag in your contact mode parameter if you want friction to act more Coulomb-ish.... i.e. more mass = more friction. Without dContactApprox1, friction opposes motion in a direction perpendicular to it's normal by a max of mu. So heavier objects would take longer to slide to a stop than lighter ones. There's no easy way to "invert" a geom that I know of. You probably just want to define each side of the box with it's own plane.
G/[email protected]	Here's an idea that might be interesting to add to the collision toolbox: primitive-mapped heightfields. For example, you have a mesh of an arm that kinda halfway looks like a capped cylinder but not really. So you take a capped cylinder, make a function to map it's surface to 2D (i.e. the long axis is x and degrees around it is y). Then you could specify heights in terms of 0 = directly on the surface of the primitive, negative means that many units towards the center, and positive means that many units away from the center (all in body coordinates if I'm clear as mud). Nothing would happen until an object collided with the surface of the primitive, then the collision system would query the heightfield at that x,y coordinate (or you could just do it yourself). This should be a lot faster than generic mesh collisions while still being able to define the exact same shape in many instances. Just a thought, P.S. in other news, I would have released the iterative algorithm today if I had not have discovered a strange small amount of torque creeping in to the system, seemingly in the friction approximation. I'll try to track this down tomorrow and see if I can get it released. I may release it tomorrow anyway so I can get some help finding the problem if it doesn't become apparent rather quickly.
G/[email protected]	Right, but as soon as that external force is applied, those bottom joints would become crushed under the weight of the wall.... unless you disabled gravity until the wall crumbles, but that has its own problems. Well, I'll have to think on this one for a while (and get a verlet integrator running at some point), but I see a few problems.... a particle mesh is 2D, so you simulate the face of the wall, and have to have something to stabilize it. There is no feedback for how much force (strain) is being placed on this particular constraint, other than how far off it is at the end of the iterations, but you could still use that as a break parameter. I kind of have a feeling that you would end up ripping a seam straight up from the impact point, then the rest of the bricks on either side would flap around like.... cloth. But I don't know without trying it, and I want to get the iterative solver completed, optimized, and integrated before I start on the next tangent. http://graphics.ethz.ch/~muellerm/publications/fracture.pdf if you're interested... Theirs is probably the method I would use at first glance, since deformable bodies are modeled as rigid bodies until they need to deform (or fracture). It would be interesting to be able to shatter glass and warp plastic in ODE... There's just not enough hours in a day.
[email protected]	After kernel upgrade, changing brightness takes some seconds and causes system slowdown if i try to change more than one level at a time. This problem does not happen in the other kernel packages i have installed(3.16, 4.3). I'm using Gnome desktop, the problem happens when i try the change through the menu at the top bar and especially if i try using fn keys to do it. If a hold fn+f5 or f6 all the way to minimum or maximum, the action causes severe slowdown in the system making it unusable for some time. I have theses modules installed in all the kernel packages as can be seen below the result of "dkms status" command. bbswitch, 0.8, 3.16.0-4-amd64, x86_64: installed iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul uvcvideo crc32_pclmul videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core v4l2_common videodev sha256_ssse3 asus_nb_wmi media iTCO_wdt asus_wmi drbg mxm_wmi iTCO_vendor_support ansi_cprng efi_pstore snd_hda_codec_hdmi arc4 snd_hda_codec_realtek snd_hda_codec_generic aesni_intel glue_helper ablk_helper ath9k pcspkr ath9k_hw ath3k evdev ath btrtl btbcm btintel serio_raw bluetooth i915 snd_hda_intel i2c_i801 snd_hda_codec snd_hda_core cfg80211 snd_hwdep rtsx_pci_ms snd_timer rfkill memstick drm snd lpc_ich mei_me soundcore i2c_algo_bit shpchp int3403_thermal wmi int3402_thermal int3400_thermal battery ac int340x_thermal_zone video acpi_thermal_rel tpm_tis tpm button processor fuse parport_pc ext4 crc16 mbcache cdrom sd_mod rtsx_pci_sdmmc scsi_mod mii fan
[email protected]	My apologies if this question has been addressed before: I'm setting up an IPfilter/NAT router configuration for a Solaris 10 system (192.168.0.1) where hme0 is the internal interface and hme1 is the external Internet interface. I want only one system (192.168.0.5) Solaris 10 via ssh however all internal systems need to pass traffic pass in quick on hme0 from 192.168.0.0/24 to any keep state for internal systems Internet access for a specific system ssh access to the Solaris router It seems that by including the first rule that ALL internal systems would have ssh access to the Solaris router which would make the second rule pointless. Is there a way to permit all internal systems access to the external network but only give one internal system ssh access to the router?
[email protected]	Exactly Mukund: We use Splunk to analyze the querylogs and we use a regex to drop unnecessary data. I had to make the change in our regexes to avoid licensing issues. I did not file a bug report because now that I've made the Splunk config changes, changing it back in the querylog format will once again invalidate my regex. My criticism was not with the addition of the new data, but rather it's location. It seems to me that right after the word "client" should come client data (like an IP address or host name), not the memory location for the running process. Thank you, though, for your work on a fantastic piece of software.
[email protected]	I installed Suse 9.2 Pro 64 bit version and as expected the fonts looked horrible. Then I followed the usual drill: (1) installed freetype2 srpms, enabled bytecode interpreter, rebuild the rpm and reinstalled it, (2) installed Microsoft true type fonts via Yast online update. Everything went fine, I have gorgeous fonts that rival even MS Windows which I see at some people's PCs. However, when I call a 32bit application eg Eclipse, Thunderbird 32bit etc ugliness comes back. But only with the 32 bit applications. The 64 bits applics are always fine. I looked into the freetype2 srpm searching for a clue as to how to uptade 32bit freetype2 libs with bytecode enabled to no success. As a last resort I downloaded freetype2 sources, enabled bytecode and compiled it on a 32bit machine. Then I copied the directory and installed the binaries on my 64 bit Suse thereby updating the 32bit freetype2 libs under /usr/lib. However, this was not successful. But to my surprise it did not screw up anything either. Any suggestions would be greatly appreciated.
[email protected]	I ran into the following difficulties when debugging in Eric. 1) I start debugging, all the debugger control buttons become active (step, stop etc..). I select continue and the debugger runs until the first breakpoint. While the debugger runs, the control buttons disappear, and I have to wait until it hits the next breakpoint. However, sometimes a particular code segment takes long to run (by design), and I may want to stop the debugger and start over, or I may want to check some variables in the meantime. I cannot do that as it is. My only option to stop the debugger is to kill the process from the shell. If there is a way to do this within eric3 please let me know. Otherwise , I would like to add this to the wish list. 2) Often times during debugging I need to isolate a few variables and follow their progress as I step through the code. As it is I can only filter out the variables I do not want to follow in the debug browser. In order to achieve what I want, I have to devise devilishly clever (or complicated) regular expressions to filter out all but the few I am interested. Is there a way to negate a regular expression in the debug window ? If so please let me know how I can accomplish that. Otherwise here is another feature request. Please add another tab to the debug browser. In this new tab, I should be able to set the name of a variable (say as a regular expression) to add it to an isolated watch list. So the set function would work in the opposite way compared to the current one. This feature would be very useful. Thanks for developing this great piece of software.
[email protected]	I just installed the Feb-12 SC7 (Windows) On a PC with 2.26 GHz processor and 1GB ram: Music Scan Details Merge Various Artists (5596 of 5596) Complete 00:01:59 Artwork Scan (6479 of 6479) Complete 01:34:50 SqueezeCenter has finished scanning your music collection.02:32:17 This was with every other program shut down. The PC was completely unresponsive the whole time, with the CPU pegged at 100%. I've got artwork imbedded in each file. Also, the controller could not fine SqueezeCenter during the scan...actually, it still cannot find SC7, so that's probably not a scan issue
[email protected]	I'm trying to make an html message formatter along the lines of the one in the docs. I've got it working for the most part. One builder is returning back utf-8 encoded logs that are causing the formatter to raise an exception when it sets the 'body' in the return dict: exception.UnicodeDecoderError: 'ascii' codec cant decode byte 0xe2 in position 55: ordinal not in range(128) I tried making the \n unicode: u"\n", but that makes no difference. Ideas?
[email protected]	I need a some advice on constructing the tests. On the CVS side of things, my buildbot-cvs-mail script is executed by CVS. Its passed some command line args, forks, reads from stdin, and sends a mail via a smtplib.SMTP() connection. Making a full test that goes through the mail server is a bit problematic. I could make simple mock for the 3 smtplib methods that are used and send the results to stdout when testing. I've got driver script sends fake CVS output, though it does not read the mail generated. The buildbot side is more difficult for me. I created a new subsclass of MailDirSource called BuiltbotCVSMaildirSource. It just implements the parse method. At the top of mail.py, I see: # -- test-case-name: buildbot.test.test_mailparse -- but don't see a test_mailparse anywhere. Is that just a placeholder?
[email protected]	for a recent project i made a grades file (based on the BCRE-example in therion distribution) for UISv1 specifications (see attachment). It would be a pleasure for me if it is useful to somebody; it would also be very nice if i could get some feedback on it. With the naming i had the intention that exporting from databases is easily doable. The prefix is "UISv1_" followed by the actual grades number. I included all the grades to faciliate documentation inside the th-files, so one can stright export "-1" surveys too. For better archiving and searchability, here is the code reproduced: grade "UISv1_-1" -title "UISv1 ungraded survey without map" # Grade 1: sketch from memory, not to scale # 95.44% of readings are within 1.0 degrees (2 S.D.) # 95.44% of readings are within 0.25 degrees (2 S.D.) # Grade 1: sketch from memory, not to scale # 95.44% of readings are within 1.0 degrees (2 S.D.) # 95.44% of readings are within 0.25 degrees (2 S.D.)
[email protected]	Thank you for the fadt reply. If i understand and interpret correctly, the behavior unfolds in the following way: - when i detect inproper morphing of walls compared to lrud data - i place "extra" points on my traced wall signature. - the extra point position is approximately where the lrud point is assumed to be on the wall. - when rendering, therion morphes the wall to match the extra point position to the corresponding lrud position for that point (which is the nearest station). That would imply: a) there is no use for extra points without lrud data. b) extra points reference l+r positions of lrud data of the nearest station, therefore it is not possible to set more than two extra points per station. Is the above true?
[email protected]	Debian install of what? I thought we were talking about player firmware (Radio or Touch). I guess you mean either LMS or desktop Squeezeplay. For Squeezeplay the git revision is in the package filename: squeezeplay_7.8.0~22901ff_all.deb. For LMS the revision used, in both the filename and as reported via the WebUI, etc., is the Unix timestamp of the revision: logitechmediaserver_7.8.0~133664662_all.deb. It is not trivial to correlate this with the git revision-id but it should also not be that difficult.
[email protected]	Hope this email find you in best of good health. We introduce ourselves as Business Development Manager's a Sub-Company Of quastels Ltd in Uk.We are looking to get a new suppliers on some of your product but first we need to know if you ..... 1.You Can ship to United Kingdom or Kingdom of saudi Arabia? 2. Advice on payment terms warranty. 3. Delivery time for F.O.B. Also kindly send us your latest catalog and price list as attachment for our study and immediate placement of our Purchase Order. Note: Pls reply asap direct to my email: (O+FPyrHlo3/[email protected]) Waiting for your s 'wift response. Your early reply will be highly appreciated.
[email protected]	Found the problem...the issue that I had was the following: I didn't realize that the webapp that I was trying to change was using a redirect servlet in a different project (which didn't implement CometProcessor). Once I disabled the redirect servlet, things started to work... So that brings me to my next Comet noob question...the redirect servlet in this other project extends HttpServlet and only has an init and service method defined...how do I integrate that with CometProcessor? Do I still implement CometProcessor and leave the event method empty? I'll start with trying that first, but wanted to know what people recommend before I just hack at it... try the simplest thing first, upgrade to 6.0.16, in terms of your config, you have tcnative-1.dll in your PATH, but you haven't configured the APR connector, you have configured NIO (which works for comet) and the regular blocking (which doesn't work for comet)
[email protected]	Just have a quick clarification for those who have done this...if I have an xml object that looks like this: <batch> I'm trying to parse over this xml and based on the tag and x I want to call a specific function passing it y... e.g. if (foo && blee) createObject(2) to decode this, would this work? Or am I misunderstanding it? for (var tag in parsedNode.batch[0]) I feel as though I am not accessing things correctly...mind sheding some light on how I would parse the info out properly?
[email protected]	1. In PPC MMU_init sets up kernel page table for all the physical pages available(say size is A) to the virt address starting from PAGE_OFFSET to (PAGE_OFFSET+A). Question: does the linux ever touch this section of page table(virt address from PAGE_OFFSET to PAGE_OFFSET+A) again? like remove or modify one of the entry? 2. In VMALLOC, say we have virt address B(B>PAGE_OFFSET+A), sets up the page table entry for this B to any one of the physical pages. Question: For every physical page, it should already be mapped in #1, but vmalloc maps it again to a virt address higher. Does it mean in kernel page table, we may have two PTE entries pointing to the same physical page, even their virt addresses are different? Last question: If this is true, is this platform implemention specific? Does i386 implemention have same situation?
[email protected]	I am looking for a replacement for MS Visio? I want to be able to do some box drawings and basic maps and designs similar to what visio can do! With my move for a linux desktop rather than what I was used to in the past for just servers, I am having to see if I can source some alternatives for some fairly handy software packages.
p/[email protected]	Thank you for this great work. I have just tried the acts_as_taggable lib with the just released gem but I encounter a problem with Postrgesql. The generated SQL code when using find_tagged_with :all is similar to this: SELECT bookmarks.* FROM tags_bookmarks, bookmarks, tags WHERE tags_bookmarks.tag_id = tags.id This code is rejected under Postgres with the cause being that GROUP BY forces the SELECT part to only reference columns that appear in the GROUP BY clause or columns with an aggregate function applied. Here, we try to select all columns but only the bookmark.id column appears in the GROUP BY. This code would also be invalid under Oracle. A valid version in Postgres/Oracle would be something like this: SELECT bookmarks.* I hope this helps.
[email protected]	For me, THE benefit to using dbpoweramp's converter is that it allows you to delete the original file after the conversion. When converting a large number of files like this, this can be important unless your SHN files are only filling up half your disc. It's not exactly intuitive - you add a DSP action to the conversion which is called "delete" or something like that. In order to get this capability, you have to pay for the base dbpoweramp package, which is quite reasonable. Short of writing a script to do the conversion, this is the only tool that I could find that would allow you to delete the files as they are being converted. You may feel you shouldn't have to pay for a conversion program, but for a small amount of money, you get a really great program. It is truely the swiss army knife for managing digital music files of all types. SqueezeCenter 7.2.1 (7.3 had dropouts for me) and SqueezeSlave. MusicIP has been turned off temporarily while I move to a lossless version of my library. http://www.last.fm/user/maggior
[email protected]	I'm using the URL Fetch api to connect to webservice in my app. When configuring the connection, I'm doing this : HttpURLConnection conn = ... A timeout of 0 is infinite with the standard HttpURLConnection of Java, but how is it used in appengine ? Doc say the timeout use is the connect timeout + the read timeout. So, is it 60000+0 = 60s, or 60000+infinite = max timeout = 60s ? If I set the connect timeout to 40000 and the read timeout to 0, the total timeout is 40s or 60s ?
[email protected]	in development/pdk/ndk, i found that android support repack the apk file manually. shall we support to do it automatically? for example, developer can make a new dir in res/ with the name which android can not identify, such as abc/. once the application passes the compilation and apk is made, that dir will appear in /data/data/ packagename/ after the apk is installed. that is /data/data/ currently, we can repack the apk file with our jni lib, if the lib is put into lib/armeabi. i hope this process could be automatically. another issue: can android support put the armeabi and x86 lib into one apk? i hope 1 apk can support arm or x86 system simultaneously.
[email protected]	I deploy hadoop cluster use two machine.one as a namenode,and the other be used a datanode. My namenode machine hostname is namenode1,and datanode machine hostname is datanode1. when I use command ./start-all.sh on namenode1,the console display below string, and use jps show java processs,display below string, and ssh datanode1,use comman jps,display below somethins strings so,the datanode can't run,and I find logs Next, what should I do to solve this problem。
[email protected]	the last days i've tried to optimize the startup of our dev environment. The first thing i found to optimize, is to move the annotation scanning to CDI and also disable the JSF Managed Bean handling. We could introduce a new flag (o.a.m.DISABLE_MANAGED_BEAN_SUPPORT) to disable Managed Beans and we could improve our performance in 3 parts of MyFaces. 1) Startup I already implemented a AnnotationProvider for CDI: OWB Startup with the new scanning Extension: 3465ms OWB Startup without the Extension: 3422ms MyFaces with default scanning: 3109ms Average Performance improvement on startup: 772ms 2) Disable PreDestroy handling on Managed beans See: https://issues.apache.org/jira/browse/MYFACES-3250 3) Skip registering of the ManagedBeanResolver WDYT? I would take care of it for trunk if there are no objections.
[email protected]	all right! I would also like to cleanup some code in the new branch (unused stuff, commented very old code and else...) Can i do that? What about code in the "shared" project? It it also used in other projects? Really, i like to quality and performance of myfaces but the code really needs a little bit cleanup in some places. yep, we should consider this in some months.
[email protected]	Ok, seems like @PostConstruct of a @ManagedBean isn't called anymore. Seems like the ManagedBean is instantiated correctly, the @ManagedProperty's are resolved but @PostConstruct isn't called. ManagedBeanBuilder ln213 calls the LifecycleProvider2 to do the @PostConstruct but nothing happens. Any idea why a Tomcat7LifecycleProvider is used when running with mvn-jetty? As InstanceManager http://grepcode.com/file/repo1.maven.org/maven2/org.apache.tomcat/tomcat-api/8.0.12/org/apache/tomcat/SimpleInstanceManager.java is used, which really does nothing. Should this work? I wonder how did this ever work? Tried it again and faced the same problem with MF2.2 now....
[email protected]	ib_ipoib can still be unloaded even when bonding is used (it is just that bonding should be removed first). About hotplug: it is still working well and correct me if I'm wrong but my way to test hotplug is to unload ib_mthca which is not affected by the presence of bonding. As I said, I would be happy to share the work on bonding and get reviews about it but I still think that this patch alone can be a first step. Well, what happens with bonding and IPoIB speaks for itself, doesn't it? If I can unload a module that is being referenced from the outside then I am not protected by the kernel from doing something wrong.
NeNaWCmw/[email protected]	Aha. You're interpreting the test results incorrectly. (You must be thinking that a high percentage is good...in fact a high percentage means something very different here) The log you posted indicates that you can't distinguish between the lossy and lossess tracks. You would want to see a % (p-value) of, say, 5% or less. But I'd be impressed with even 10% or less. bottom line, the results you posted indicate that you can't distinguish between the lossy and lossless file. More info on interpreting the ABX test here: http://www.hydrogenaudio.org/forums/index.php?showtopic=16295 a little on p-values and testing: http://en.wikipedia.org/wiki/P-value
[email protected]	Hey, I thought programming was all about the shortcuts ;-) I'm sorry to not be clear. I've done several excellent python + postgresql tutorials, but the one I have not found is wxPython + postgresql (or any database). Specifically, how would you take your sql results and set the values of your wxTextCtrls and wxListCtrls? For example if the sql select statement returns 20 fields the function would find the wxPython controls with the same name and set their values. And how would you build a sql statement with only the wxPython controls that have been modified by the user? So if only the address field was modified the sql would be: UPDATE table1 SET address = '123 Easy Street' WHERE rec_id = 1
ym1Chx+DltvA/[email protected]	So maybe we should create the initial package for Debian stable and then upgrade it for unstable (probably the diff will be minimal)? I might be wrong, but I think that all those problems with indirect dependencies might postpone the upload, but they should not affect the content of the package. Thats why I suggest to create the package for stable (which can be done now) and then wait until the problems with indirect dependencies settle down. Who knows, maybe it will happen in sync with us finalizing the initial package...
Z3/[email protected]	IMO, pushing obscure settings into the extension system is a mistake. If we wanted to make this a setting, we should find a place in the UI for it. There are two arguments against having user configurable settings: 1. It complicates the code base to have multiple options and requires additional testing. Maintenance burden, etc. 2. We want simple UI. #1 is certainly not solved by moving options to extensions. If anything, it makes it worse. Extension-controlled options are more complicated than a Chrome-controlled user preference. #2 is solved for the default case, at the cost of making the configured case more difficult and hard to discover (have to know about, find, and install a separate extension).
Z3/[email protected]	I am. I actually do successfully switch between branches and work on multiple different CLs at once (or single changes that span multiple CLs), so maybe my setup will be useful to you. I use 2 main tricks that make life less painful than the "obvious" git workflow. Trick 1: use a separate machine (or at least a separate checkout) as commit queue. My configuration: - Windows box with Cygwin and git. Single checkout. This is my main dev machine. - Linux box with git. Single checkout. This is my commit-queue machine (and dev machine for linux-specific work). I send all my reviews and commit the final result from this machine. - When I start a new CL, I check out a fresh branch on my windows box based on the origin: - I work on it for a while, committing as I go. When I'm ready to send for review, I log in to my linux box and grab the CL into a clean branch there, - Now I have to wait for review, so I can start a new CL on my windows box: The advantage of using a separate machine as a commit queue is that I can switch between branches on the commit-queue without worrying about updating filestamps and having to rebuild on my dev machine. I have to switch branches much more often when sending things up for review and/or committing. (You could also accomplish the same with a separate checkout on the same machine, but this has the additional advantage that I can test that it builds on linux too.) Trick 2: Switching branches on the dev machine. Switching branches on the dev machine is tricky. You want to avoid running gclient sync as much as possible. You also want to avoid switching to a really old branch, since it'll touch a ton of files that you'll have to rebuild. To illustrate my point, consider this workflow: be touched and have to be rebuilt. To avoid that, create a new branch based on origin and just merge in bar's changes: will be touched, and there will be much less rebuilding. I've set up a git
[email protected]	ApplicationServlet.could-not-locate-engine=Could not locate an engine to service this request. ActionService.context-parameters=Service action requires either three or four service contect parameters. 1.1 jakarta-tapestry/framework/src/org/apache/tapestry/util/ContentType.java * modification, are permitted provided that the following conditions * * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * notice, this list of conditions and the following disclaimer in * the documentation and/or other materials provided with the * distribution. * * 3. The end-user documentation included with the redistribution, * if any, must include the following acknowledgment: * "This product includes software developed by the * Apache Software Foundation (http://apache.org/)." * if and wherever such third-party acknowledgments normally appear. * must not be used to endorse or promote products derived from this * software without prior written permission. For written * permission, please contact [email protected]. * name, without prior written permission of the Apache Software Foundation. * SUCH DAMAGE. * This software consists of voluntary contributions made by many * individuals on behalf of the Apache Software Foundation. For more * information on the Apache Software Foundation, please see * <http://www.apache.org/>. * the mime type, the character set, and other parameters. * This is similar to a number of other implementations of the same concept in JAF, etc. 1.1 jakarta-tapestry/framework/src/org/apache/tapestry/util/LocalizedResource.java * modification, are permitted provided that the following conditions * * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * notice, this list of conditions and the following disclaimer in * the documentation and/or other materials provided with the * distribution. * * 3. The end-user documentation included with the redistribution, * if any, must include the following acknowledgment: * "This product includes software developed by the * Apache Software Foundation (http://apache.org/)." * if and wherever such third-party acknowledgments normally appear. * must not be used to endorse or promote products derived from this * software without prior written permission. For written * permission, please contact [email protected]. * name, without prior written permission of the Apache Software Foundation. * SUCH DAMAGE. * This software consists of voluntary contributions made by many * individuals on behalf of the Apache Software Foundation. For more * information on the Apache Software Foundation, please see * <http://www.apache.org/>. package org.apache.tapestry.util; 1.1 jakarta-tapestry/framework/src/org/apache/tapestry/util/LocalizedPropertySource.java * modification, are permitted provided that the following conditions * * 1. Redistributions of source code must retain the above copyright * notice, this list of conditions and the following disclaimer. * notice, this list of conditions and the following disclaimer in * the documentation and/or other materials provided with the * distribution. * * 3. The end-user documentation included with the redistribution, * if any, must include the following acknowledgment: * "This product includes software developed by the * Apache Software Foundation (http://apache.org/)." * if and wherever such third-party acknowledgments normally appear. * must not be used to endorse or promote products derived from this * software without prior written permission. For written * permission, please contact [email protected]. * name, without prior written permission of the Apache Software Foundation. * SUCH DAMAGE. * This software consists of voluntary contributions made by many * individuals on behalf of the Apache Software Foundation. For more * information on the Apache Software Foundation, please see * <http://www.apache.org/>. * capability of searching for localized versions of the desired property. * of more specific to more general and returns the first that has a value. while (generator.more())
[email protected]	1.1 jakarta-tapestry/framework/src/scripts/TestFor.xml Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. <mock-test> Do not show this Do not show this either But show this too! Do not show form text Do not show this form text either But show this form text too!
[email protected]	I am doing a project to decouple the business domain (entities) from persistence mapping, by converting annotations to XML. Doctrine:orm:convert generally works fine, but I encounter some issues when converting mapped superclass hierarchies, and I am looking for an answer to a related question: 1. The resulting XML mapping gets a table attribute defined in the <mapped-superclass> element (<mapped-superclass name="\Some\Abstract\SuperClass" table="SuperClass" /> This is unexpected because a mapped superclass is a non-entity 2. Field mappings defined in annotations in the superclass are not generated in XML Are those two issues expected behaviour or bugs? If those are bugs I'll be happy to open tickets for them :) The related question I have is what mappings can be defined on the mapped superclass that will be correctly inherited by the concrete subclasses? I have property mappings (@ORM\Column), but also @ORM\UniqueConstraint, @ORM\Index and @ORM\Id annotations. I'd love to be able to define them in the mapped superclass XML as much as possible so they can be inherited by the subclass entities. Suprisingly enough traits with mapped properties seem to be handled correctly: the property mappings appear in the generated XML for the entities using the traits. This seems to be correct under the assumption that traits cannot have their own XML mapping.
[email protected]	I am doing a project to decouple business domain (entities) from persistence mapping, by converting annotations to XML. when converting mapped superclass hierarchies, and I am looking for an answer to a related question: 1. The resulting XML mapping gets a table attribute defined in the <mapped-superclass> element (<mapped-superclass name="\Some\Abstract\SuperClass" table="SuperClass" /> This is unexpected because a mapped superclass is a non-entity 2. Field mappings defined in annotations in the superclass are not generated in XML Are those two issues expected behaviour or bugs? If those are bugs I'll be happy to open tickets for them :) The related question I have is what mappings can be defined on the mapped superclass that will be correctly inherited by the concrete subclasses? I have property mappings (@ORM\Column), but also @ORM\UniqueConstraint, @ORM\Index and @ORM\Id annotations. I'd love to be able to define them in the mapped superclass XML as much as possible so they can be inherited by the subclass entities. Suprisingly enough traits with mapped properties seem to be handled correctly: the property mappings appear in the generated XML for the entities using the traits. This seems to be correct under the assumption that traits cannot have their own XML mapping.
[email protected]	http://bugs.kde.org/show_bug.cgi?id=63770 It would be fine to have an option for not adding m3u (and other) playlists on my defined directories to the playlist's list. This way I shouldn't have to remove them after restarting the app. It's great to have the option of adding dirs for initial scan, but it's a PIA when these m3u files re-appear on the playlists' list every time I restart juk.
[email protected]	Many thanks for your swift help -I think the mp3tag software will do the trick - it looks quite whizzy! Having known next to nothing about tagging a couple of hours ago - that makes it seem quite easy! The other tags are there....just the artist that is missing...so I reckon it will be quicker to just go through all of what I've ripped already & add the artist names in the appropriate box...then I can keep the year, genre etc. Any ideas how I get EAC/FLAC to add the artist tag for the rest of my ripping future!!??? I looked at the EAC link - many thanks - which is how I set it up originally (I think)..except I am using compression 8 rather than 6.
[email protected]	Maybe a note should be put onto the voting page - like "Remember that this splash screen will be shown to a lot of users, many of whon are not computer freaks or experts. Therefore, the splash screen should be worthy a respectable image manipulation app.". Just randomize them - use a seed value based on the nickname so that the page looks the same every time. My k.o. criteria: - just a photo - screenshot with OS-specifics (e.g. window decoration) - advocacy Mirrors, anyone? Votes are easy to add... ACK. The voting pages should close automatically (and communicate this clearly).
[email protected]	So it might make sense not to interleave tiles but let each thread start on another region of the image, like this (for 4 threads) So each of the threads works on "it's own" memory at first and only when it finished it's region, it will get tiles from the remaining work. Some binary-search like algorithm could be used like this: - figure out largest remaining part of the image (at start, it's the whole image) - let x be the number of idle threads - if starting up, divide into x regions divide into x+1 regions assign idle threads the x+1st, x-th, x-1st etc. region (this leaves the first to the thread currently processing it) - start processing the regions - if any thread runs out of work, restart algorithm This should improve memory locality while distributing work across all threads and making sure that non-uniform workloads are also distributed. Consider the above example where thread 4 has finished it's tiles: It looks like 1 will need the longest time to finish it's region, so we jump in there and assign part of it's work to 4 (marked y): Later, 3 finishes: Now, 2 has the largest region left, so half of it get's assign to 3 (marked z): The state of affairs can be managed easily since there are never more regions than threads. PS: I don't know whether this algorithm works well in practice, I actually got the idea while replying Adam's response.
[email protected]	To get some details into the game - a while ago (just after 2.2 was released), I tried upgrading to 2.6 (I thought that 2.6 was required, but this doesn't matter here). I ended up with a system where - gdm crashed (I was unable to get any useful error message - logging seems to be broken with regard to this, strace did not help) - GIMP 2.2 crashed almost every time I opened the file selector with some strange pango message showing up (some assertion failed) - it seems that font handling has somehow changed (I did compile a new pango, but not a new freetype) I found an obscure way to prevent this crash, but I cannot remember anymore - it was not really stable either. - OpenOffice stopped working with some unresolved symbol _XineramaIsActive I straced a lot but got no real conclusion (apart from that the new file selector opens a lot of files which probably kills performance on networked file systems). I can give it a try tomorrow and see whether I get some useful error messages. (My earlier message to this list describing my problems has somehow been ignored, there might be some details in there.)
[email protected]	I'm having problems installing FC4 on an Intel 7221BK1-E motherboard. If I try to install from the FC4 CD, it panics immediately after loading vmlinuz and init, so I used the "trick" from http://www.ulkuderner.net that involves using another CD until it asks for "where to load", and then switching to FC4 CD. Only problem is that video is recognized as VESA generic, and the xserver does not work (it starts correctly, but no video is shown). If I use Red Hat Enterprise 4, it works. Problem is that I need graphical installation on FC4 to create logical volumes and RAID 1 partitions (no logical volumes can be created under text installation). I tried with noprobe and resolution=640x480, but to no avail. Any suggestions?
[email protected]	Thank you for your welcome to this list, and for the initial comments about using Borland C++ Builder to compile Audacity. Not being a professional programmer, who only goes into the deep end when he needs a certain application constructed to accomplish a specific task, it takes me a while to get a sense of the landscape. Now, it appears to me, after looking at the Audacity source code, and studying the issue of wxWidgets, that this is a purely C++ application, with nothing specific to any particular development environment. And in theory, the only thing you need to compile it, is an industry standard C++ compiler. Microsoft Visual C++ is mentioned in relationship to compilation for a windows platform, not because Audacity uses anything within Microsoft Visual C++ proprietary libraries, but only because this is the industry standard C++ compiler that the Audacity developers were most familiar with. Theoretically then, because the C++ compiler inside of Borland C++ Builder 5.0 and later, is industry standard, and there is nothing inside any of the Audacity source code but pure C++ code, there is no reason why BCB should not be able to compile this project. (From the Box: "Used the latest in ANSI/ISO C++ compliance support ....") Does anyone see any glaring fault in this logic?
[email protected]	I appreciate your comments, though I think that we need to make an effort to be on the same page here. From README.TXT in the Audacity (1.2.3) root directory: "To compile on Windows using MSVC++, please follow the instructions found in compile.txt in the "win" subdirectory." "Audacity releases to date have been built with Visual C++ 6.0, with Service Pack 5." The implication is, that this version (1.2.3) can be also and that all the files included are configured for this. "Audacity can be built with Visual C++ .NET 7.1. Let Visual Studio automatically upgrade the .dsp project files." Note that it says "can be" and not "must be", affirming the above implication that this release should be able to compile with Visual C++ 6.0 (SP5). The only thing the text points to in regards to modifications that the user must make when compiling with Visual C++ .NET 7.1. relates to soundtouch. Here is the full paragraph: automatically upgrade the .dsp project files. Then manually fix the soundtouch project file: Remove all the .cc files from the project, then re-add them (except for mmx_gcc.cc, which for some reason is not converted correctly). You might also have trouble with the precompiled headers in the Audacity project itself - you can fix that release build configuration, you have to remove "libci.lib" from the And then, after discussing the compilation of WxWidgets, and directing the user to download the Audacity source code, the author goes on: "Run Visual C++ and load the Audacity workspace: it's "audacity.dsw" in the "win" directory of the Audacity source tree." Note the extension of that file ".dsw". This workspace file points to other project files with the ".dsp" extension. And so, then, I am following the information in these files to pattern a compilation strategy for Borland C++ Builder 5. I can't see, from what you have said, why there would be any particular problem with this. Moreover, when you say, "so you should ignore those MSVC++ 6 workspace & project files and work strictly from the .vcproj files." This is the more confusing for me, because there are no files in the Audacity 1.2.3 installation with the extension ".vc" anything. So, please respond with an explanation that will help me reconcile your comments, with what is written in the Readme.txt, and Compile.txt files, and especially in regards to the fact that it appears that the only MSVC++ files that are included are those with the ".dsw" and ".dsp" extensions. (did somebody forget to include the new Compile.txt file, along with all of the Visual C++ .NET 7.1. workspace and project files? That would explain the confusion I suppose). I am all ears. P.s. The "problems" I have pointed out so far, in terms of non-existant paths, are indicated at the very first stage, in adding source files to the Borland project, and I only mention them, because it appears to be an error that ought to be fixed by those who maintain the .dsw and .dsp files. They all appear to be minor (non-source code) files, except for the soundtouch path which is completely wrong. Steven, sorry I haven't been reading your messages more closely, but I know nothing about Borland C++ Builder. Your messages from yesterday evening raised a red flag for me, though. I don't think you'd mentioned before that you're going from the .dsw & .dsp files. I believe it says in the compile.txt files (definitely for HEAD and I'm pretty sure for AUDACITY_1_2 -- I don't recall which you're working on) that the standard for Audacity is now MSVC++ 7, so you should ignore those MSVC++ 6 workspace & project files and work strictly from the .vcproj files. That may be the cause of much of your problems. It's no surprise that the *.dsp files would be out of sync with the source code. I completed the upgrade in December. And make sure that if you're using HEAD, you're using wxWidgets 2.5.3, or if AUDACITY_1_2, that you're using wxWidgets 2.4.2. I believe that's in the compile.txt files, also. I'd be more specific, but I had to do a complete overhaul on my development machine the past few days and don't have Audacity development restored yet, and I wanted to get this info to you ASAP.
[email protected]	I found the original driver files for the soundcard, downloaded the file, and reinstalled. The problem is still there, and the File Monitor sequence I posted earlier is the same. The fault report process is invoked directly after several calls to that audio driver "wdmaud.drv". As far as the error reporting data goes, I can look at that by clicking on the links in the error dialogs. It allows you to drill down to a window that displays a description of all of the modules that were invoked, in the order they were invoked, and their version numbers. In this case it validates the observation made above, that the fault reporting dll is called after the audio driver is accessed multiple times. But after that, it appears to be a big long memory dump, and there is no way to copy it to the clipboard, so I can't reproduce it here. (the text selection function is disabled). I am open to any other ideas on what I might try next. The installation of all of those other programs I referred to initially, and their uninstallation, (though I am not sure if the problem was there as the result of the installation, or the uninstallation), has changed something which Audacity is not handling. The situation is invoking an error that Audacity is trapping, though I suppose it is one that is not anticipated, in as much as there was no effort in the code to recognize it, and handle it. What is it, that would cause Audacity to decide that it can't proceed at this point? This is very earlier in program execution. The program window is not even displayed yet. So the place where this is occurring would have to be in the first initialization code. Perhaps in the constructor for the main form. Is the person who programmed that code still around? "rebuild" the registry entries. Don't know. I'd certainly give it a go. I don't...didn't know I could???
L/AukyaNhuOUdC/[email protected]	I've used CrystalBond to mount wafers for dicing. Brewer Science has several products including Protek and WaferBond that might be suitable. I'd like to use an intermediate material to "bond" device wafer to dummy Si wafer for dicing. The "bonding" strenth may not be very strong. The main goals are to reduce chipping on the device wafer during dicing, and easy to clean at the same time. positive photoresist could be an option.. Does any one know any material that is suitable for this application? It could be low cost, not toxicate, and easy for cleaning
L/AukyaNhuOUdC/[email protected]	I wonder if a PDMS bond between two wafers will withstand a KOH etch, or will the interface fail? KOH doesn't affect PDMS I wanted to know if anyone of you has an experience with performing EDP/KOH etch of a Si wafer with PDMS or photopatternable silicone WL 5150 patterned on the back side. Does the EDP/KOH etch damage the PDMS or the photopatternable silicone? Thank you very much,
L/AukyaNhuOUdC/[email protected]	Another etchant that works well for Ni is Aluminum Etch, which contains phosphoric and nitric acids. If you just want to strip the Ni you can use Piranha. Does anybody have experience of using Transene nickel etchant (TFB) with concentrated Nitric acid to etch Nickel on Silicon? I need to etch Nickel from SOI wafer (220 nm Silicon on top of 1 um buried oxide layer), I wonder if nitric acid present in Nickel etchant will etch Silicon too. At present, I need to soak the sample in nickel etchant for 10 minutes to remove 25 nm of nickel (slow rate of nickel removal due to plasma processing of sample with nickel on it, normally evaporated nickel is removed in 2 minutes but after plasma etch, it takes a lot longer).
L/AukyaNhuOUdC/[email protected]	As I understand, the modification you're making is the addition of the thick oxide under the nitride. Growing such a thick oxide will take a long time e.g. ~49 hours for a wet oxidation at 1100 degC. An alternative might be to use an oxide or other dielectric deposited by CVD. If you use SiO2 as a dielectric it might be better to wet etch with BOE, since the CHF3/O2 RIE will probably etch the nitride faster than the nitride. I'd like to ask for advice on how best to modify the standard procedure for fabricating suspended silicon nitride membranes to incorporate a thick dielectric layer (>=5um). The aim is to reduce the capacitance from the top to the bottom of the chip supporting the membrane, as it will be used to separate two chambers of conductive fluid. The capacitance with standard membranes is very high since the thickest dielectric layer is the thin silicon nitride (50-100 nm in my case). Reducing the fluid contact area will reduce the capacitance, but the microfluidics required to achieve an equivalent reduction in capacitance appears more complicated than adding a dielectric layer. (The particular application I'm working on is nanopore-based DNA analysis, where the noise level scales with capacitance. For background info see http://eleceng.ucc.ie/nanopore/) The best process I have come up with so far is as follows, but it's still significantly more complicated than the standard procedure for silicon nitride membrane fabrication. See the diagram below for reference. 1. Grow 5 um thermal oxide on 100 silicon wafers (on both sides to avoid wafer bow due to stress) 2. Grow 50-100 nm low-stress silicon nitride on top of the oxide 3. Follow the standard membrane fabrication procedure to define openings in the mask nitride layer. 4. Anisotropically etch the mask oxide layer with CHF3/O2 plasma, protecting the silicon nitride with photoresist. 5.KOH-etch the silicon following the standard membrane fabrication procedure. 6. Finally, etch the exposed dielectric oxide with CHF3/O2, protecting the membrane silicon nitride with photoresist. 7. Remove any fluoropolymer residue resulting from the CHF3/O2 etch with oxygen plasma. Any suggestions would be greatly appreciated.
[email protected]	I'm working with a custom plugin that extends GstBaseSink. I add this and a queue to my pipeline. E.g. I link this queue/GstBaseSink pair to a decodebin2 manually when a video pad appears. E.g. this); The difficulty I find is that my GstBaseSink causes the pipeline to pause. It doesn't grab the buffers and so the queue fills up. This pauses the stream both upstream and downstream. What I'm wondering is whether this is a) Because I'm using an appsrc, but I'm not setting the timestamp properly. E.g. of b) should I revise the GstBaseSink to restart the pipeline? (Don't know what the code would look like)
[email protected]	See my comment below. The first slash / of the pathname of your .htpasswd file, should also be the root of your web server, as shown by In other words, this variable value will be added before this first slash, so the web server be able to get the correct file pathname. Indeed you specified the .htpasswd pathname as if the web server was aware of the entire file system of your machine, which is not the case.

End of preview. Expand in Data Studio

README.md exists but content is empty.

Downloads last month: 84

Size of downloaded dataset files:

3.01 GB

Size of the auto-converted Parquet files:

3.01 GB

Number of rows:

4,532,782

Collection including Hieuman/gmane_dataset-doc

Document-level Authorship Datasets

Collection

25 items • Updated 8 days ago