Best Practice EPA files...

Hi,
i found the the following EPA files from SAP Best Practices for Portals- V1.70 :
1)BP_ALL.EPA
2)BP_EC_ALL.EPA
3)BP_ECC_BL.EPA
....The question is that whether i can use the "iviews" in these files to give to my users ...or whether this iviews are only for demo purpose(i could see that this are a prototype files)....if this files are a prototype ....can i find the original EPA files...any where else?
Rgds,
P.Navakanth

Apple has already hidden about half of the folders on a typical OS X install. The ones that make up the Unix core of the OS. So unless you know how to find those, you'll never have to worry about them.
Aside from that, you just want to keep away from the System folder and any of the Library folders. Nothing else should be too crucial to the OS running.
Of course if you wanted to elaborate on "a little strange" we might be able to be a bit more helpful.

Similar Messages

Best Practices for File Organization/Project Explorer

So we are finally getting SCC at my organization to manage our LabVIEW development, and that is good!
Now, we are starting in on discussions about how we should organize our files on disk and how we should use the Project Explorer. When I started here about 3 years ago, I wasn't very familiar with the project explorer, so I read the article at http://zone.ni.com/devzone/cda/tut/p/id/7197. Two of the main things I took away from that article are:
1. Organize Files in a logical manner on disk. Whatever that is, it is not a flat file structure.
2. The top level VI should be separate from other source code. Preferably, it should reside in the application folder.
Push Back Against These Recommendations
Before I was hired, most, if not all LabVIEW development was done utilizing a flat file structure and the top level VI lived with the source code. Since we didn't have a proper SCC, each individual organized files as he saw fit. So I started using the Project Explorer (not even its use is totally accepted right now) and I began follow recommendations 1 and 2 above. I didn't always follow #1 very strictly, but I have been working towards it, and I have always followed #2 religiously.
Since we are starting these discussions on how we should organize files on disk I'm starting to get some push back to following these two recommendations.
The arguments I get in favor of using a flat file structure is that you always know where every file is; including the top-level VI. It is also argued that it is a lot of effort to organize and search for VIs when they all reside in different folders. I think the fear is that by getting "clever" and organizing our files in such a manner we'll make things complicated and we will somehow shoot ourselves in the foot.
The argument I get against separating the top level VI from the rest of the source code is that it:
(a) Won't be clear where it is (like it is buried within hundreds of VIs). However, it is argued, you can just put a "!" in front of the file name and then it is always the at top of the flat file structure.
(b) An extension of argument of (a) is that things either look or seem messy when VIs (including top level VI) don't live in a sub-folder and are just hanging out with the Project Explorer file.
(c) I think there may be some fear of breaking the VI by moving it and altering the dependencies for the VI.
Convincing Others its Good to Follow These Recommendations
So, if I want to follow NI's recommendations, I need to come up with reasons we should follow these recommendations. Also, I should state that I care about following these recommendations because its what NI recommends. They've been around the block a few times and I'm sure there are good reasons why these are best practices. However, I don't think I've given a very compelling case for why these recommendations should be followed.
So I'll tell you all what I think good reasons are for these recommendations and perhaps I can get some feedback or additional support? If I'm crazy for wanting to follow these recommendations maybe someone can point out why I'm crazy.
(a) Arguments for Following Both
I. I passed the CLAD a couple of weeks ago, and I have started studying for the CLD. Part of the CLD is following both of these recommendations (see page 6 of http://ftp.ni.com/evaluation/certification/cld/cld_exam_prep_guide_english.pdf). While this isn't a reason in and of itself, it suggests that if it important when being certified it is important in practice!
II. If we hire new developers that are familiar with LabVIEW, they will most likely be familiar with these recommendations, especially if they are certified. That will lead to increased productivity out of the door because they won't have to learn our special way of doing things.
(b) Arguments for Organized File Structure
I. Unused VIs are easier to identify and remove. Right now we never remove VIs because we don't know if they are used or not. This leads to a lot of VI bloat.
II. It is hard to know what a specific VIs function is in a flat file structure by looking at the name.
(c) Arguments for Separating Top Level VI from Source Code
I. Placing the top level VI is an intuitive place for this VI. As long as the top level VI is the only VI in the application folder there is no mistake it is the top level VI, especially once you open it. This makes it easy for new developers to find the top level VI. I'd argue it isn't very intuitive for new developers to know that a VI in the source code folder that is prefaced with a "!" is the top level VI.
Summary
So that is what I think so far. Is there anything else I am missing to support following those two recommendations or am I just being inflexible?
Thanks!

zenthoef,
As a CLA, I have struggled with file structure over the years. Here are my recommendations:
1. Put the top level VI and the project in the top-level folder. This makes it very clear where to begin.
2. Put the remaining user interface VIs in a separate folder. Again, it makes it very clear what the functionality of these VIs are.
3. If you are using object, put each object in a separate folder. Place the family of objects in one folder, with each object in a subfolder.
4. Keep the remaining VIs either in a single folder. This can contain a small number of subfolder if your project is large, but too many folders makes it hard to figure out where your VIs are. For example, you might have a DAQ subfolder, an Analysis subfolder, and a Report subfolder. But if you had a Test1 folder, a Test2 folder, and you had a VI that was used by both tests, where would it go? Keep it simple.
5. You inferred that it is hard to figure out what a VI does by its name. That implies that 1) you need better names, and 2) your VIs are too complicated. A VI should do a single function which can be adequately described by its name. That VI might be something like Analyze Data.vi, which would contain a bunch more subVIs (like Get 1st Harmonics.vi), but each VI would contain a single function. You wouldn't save the data to a report in the Analyze Data.vi, for example.
The most compelling reason for following these suggestions is that it is easier to figure out what the code is doing after you haven't looked at it for a while. Once you have an application that is working and bug free, you shouldn't have to touch the code until you want to add features. If that is even 6 months later, you will probably have forgotten how the code works. As a consultant, I have had to update other people's code, and just figuring how where to start can be a challenge.
Tom Brass
Certified LabVIEW Architect
Saint Bernard Engineering, Inc.
www.saintbernardengineering.com
Tom Brass
Certified LabVIEW Architect
Saint Bernard Engineering, Inc.
www.saintbernardengineering.com

Best practices for file I/O within producer/consumer loops

I'm looking to add file recording and playback functionality to a pre-existing data collection program. The original progam is based on a Moore-style state machine, which I have added four additional states to. They are: Record Start, Record Stop, Playback Start, and Playback Stop.
What I have done, and what has since been identified as poor programming practice, was to "initialize" (either create or load) the appropriate file within the state machine loop during the "Start" command (for record or playback functionality), and then provide the file reference as an indicator, which is linked to for the appropriate read or write operation(whether I'm playing back or recording). The actual I/O occurs within the the Consumer Loop. (screenshots attached).
This is my first labview project outside of tutorials or other small examples, so any advise and constructive criticisims are welcomed. Specifically with regards to file IO and refnum routing (it gets a little hairy in the consumer loop)!
I'm running Labview 8.6 on Vista business.
Attachments:
Playback Start.JPG ‏71 KB
Consumer_Loop.JPG ‏122 KB
File Playback subvi.JPG ‏14 KB

jamoore84 wrote:
Ben,
Thanks for the suggestion. I think it's a little outside my ken at this moment, but I'll look it over. Despite any grevious coding transgressions, I have experienced some limited success with the current setup. While the use of Action Engines/Functional Globals may constitute the best practice, I might revise my post to read "acceptable and/or easily absorbable practices" instead.
Are there any other opinions on this? Let me start by listing a problem and posing a question:
Problem: I am able to playback a file only once. Subsequent attempts at file playback do not work.
Thanks in advance,
jimmy
HI Jimmy,
I don't give up easy.
Let me try to exaplain the issue with race conditons with a contrived example, the
"Command by Mail box" case.
Imagine you had a job where you recieved your orders via an old fashioned mail box. You never really saw your supervisor but relied on getting orders via the mail box. Now imagine the mail box could only hold one message and any time a new message was inserted, the old one would fall into the trash.
So you come to work each day check your mail box do what was ordered and everyone is happy.
The next day you come in and without your knowing, you are assigned to do the work of two bosses. So as long as you check your mail box more often than the two of them assigne work everything is fine... until you take a day of vacation! So you come back in the day after vacation and check you mail box and work a way until you catch hell for ignoring orders !?! Wel it turn out the order from boss 1 was replaced by the order from boss 2 while you were on vacation. Oh bother!
How can we fix it?
1) Expand the mail box so it hold more than one order. You just process them in the oder they are recieved.
2) Change to mail box to not accept a new order until you have removed the old.
Now back to reality!
Local variables act like the funky mail box. The last message insterted over-rides the previous.
Multiple variable writer ar like multiple bosses.
Queues operate like an expanded mail box, letting you handle each message in order.
Action Engines operate like the "mutexed" mail box.
Why I don't want to encorage you to "just patch up" what you have.
All of the less than ideal solutions either over-sample (Check e-mail twice as often as bosses assign work, waste CPU, an exercise in futility if you are coding in a non-Real-Time envirionment like Windows) or use a mutex to control access to the shared resource ( in this case local varialbes).
LV offers mutexes through semaphores (found on the syncronization pallete) but...
WHY WORK SO HARD?
In my AE Nugget I explain that the exection of an AE is automatically protected by LV. So in the long run it will actually be easier to learn how to use the AE programming construct than it will be to learn how to solve the problem without them.
so GO FOR IT! Take the lazy route and learn how to use the AE construct. Use the Syncronization pallete for Queues.
Just trying to help,
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Best practice migrate file server

I have 3 file servers n two different domains:
FileS01 and FileS02 in domainA (FileS01 / FileS02: Windows 2003R2)
FilesS03 in domainB (FileS03: Windows 2003R2)
Should I migrate to a new
corporate server to be FileS01 (Windows 2012)
also call and be in the domainA.
As you advise me to do it?
Thanks

I recommend you consult this guide:
http://technet.microsoft.com/en-us/library/jj863566.aspx
Yes, it is a ton of information but it also covers all angles; what to name the servers, when to rename the servers, using DFSN to make things smoother, the migration tools, migrating local users, etc. Due to the sheer amount of information, ignore
the areas that don't apply to your implementation (BrancheCache, as an example.) HOWEVER, I do recommend you consider their suggestion to move this into a DFS Namespace. That way the next time you need to move to a new server, the users will barely feel
it.
Best of luck.

Best Practices, Project Files with External Drives

I've found bits of discussion here and there, but I would like some further clarity.
For performance and stability is it best to have the Final Cut Pro Documents directory on an External HardDrive and the Project File on the desktop?
Ideally I would like to have all the files for each client project on a separate Hard Drive for working and storage purposes. Is this generally what others are doing? I've had some editors not do this, and I end up searching around for clips and project elements on the main hard drive, which makes me nervous that I will miss something for archiving.
Also, with some critical projects I've been making a second copy of the external hard drive at various stages of the project in case of drive failure. I guess a swappable raid system might be an option, but I really like the plug-in play of firewire, not to mention they're cheap.
Any insights into how others are managing projects, files and storage would be appreciated.
Thanks,

I keep all my projects on the internal drive (main system drive) and all the media on the externals or secondary internal drive. I back up the project files each night to one of the externals (the one with the media of the project I am currently working on) and a USB Thumb Drive. I do this redundant backup as the project file is gold...without this your project is lost. Tapes you can always recapture.
When I start a project, I designate the scratch drive. That way, all the captures and renders go to that drive. If I change projects I am working on from day to day, then I go into my settings and change the scratch drive, so that I keep things where they belong....and so they don't end up scattered across my system.
Backing up my drives? Cloning the media drives? Unnecessary IMHO. If you lose a drive, you still have the project file and you simply re-capture. And I have never lost a media drive yet...
But, it you want to be safe about it, get a RAID and make it the kind of RAID that makes duplicates of the media on several drives. Not sure what the RAID type that is.
Shane

Best practices for file architecture? I mainly have photos and music to organize.

I am moving my files from an old macbook pro to a newer one.
I want to make sure that I am more organized with this new computer than I was in the past.
Does anyone have suggestions re., how best to set up the file architecture?
Thanks!

I am moving my files from an old macbook pro to a newer one.
I want to make sure that I am more organized with this new computer than I was in the past.
Does anyone have suggestions re., how best to set up the file architecture?
Thanks!

Best practice: tar file handling through java on Linux

What would be the better way to handle large size tar files (size may be more 1 GB) on Linux using Java? One way would be by using linux "tar" command through Runtime.exec, another option is through Java zip classes?
Btw, functionality I am doing is extract the large tar file, remove some files and tar it back to make a smaller size tar ball. I am not too sure if Java provides an api to remove individual files/directory from a zip file.

A tar file is not a zip file.
Java provides no classes that handle .tar files by default.
It does provide classes to handle the gzip compression that's often applied to .tar files (resulting in .tar.gz or .tgz files).
So you either search for a library that handles tar files in Java or invoke tar as an external process.

Best practices re file locations for bootstrap, fonts, js, imgs, custom css regardless of App provisioning or Design Manager

Hi
I am working with a media company who are producing our responsive branding which includes bootstrap for a new publishing intranet. It occurred to me that I need to encourage consistency in the file locations regardless of if the files are provisioned
through an App I will build or through Design Manager and my mapped network drive.
client css
client js
client imgs
client fonts
bootstap css, and js
other frameworks: Jquery, knockout, angularjs
Previously, the the 2010 world, I tended to go for the benefits of the Site Collection libraries: /Site Assets/client/img and /Style Library/client/css and Style Library/client/js but having look at some the codeplex stuff such as Boostrap or
Responsive for SharePoint 2013 ( using _layouts/ , I am thinking I need to revisit this for both on prem and maybe office 365 stuff I am doing shortly.
Be good to get a few opinions on this
Daniel

Hi Dan the Man,
I recommend keeping them within the site that they are for, as opposed to at the root of the site collection. So not here:
http://mysiteurl.com/ but rather here
http://mysiteurl.com/sites/mysitename
Cheers,
Stacy Anothersharepointblog.blogspot.com
Hi Stacy
Thanks for your comment. In the case of my client there will be a fair amount of common stuff that will be on the top level site and also the subsites say bootstrap and certain corporate images. However, I agree, the UI will have more granularity
in the branding If I deploy your option. Say I have business area site which will have a different CSS to reflect its identity; even if has the same master page as other business area sub sites. Also, nn sites could have nn file structures
for css, js, etc which would take a bit of management.Maybe there is a "hybrid" approach I need to consider here.

Best Practices for File Management

I just wrote post about how I use Lightroom, Dropbox, and Crashplan to manage my photos. I'm curious if anyone here has a critique for my approach. I'm not a "pro" by any measure, so I'm not sure if this is a good approach, or if there are better ways to accomplish the same thing. In general, I just want a highly reliable, low pain workflow for keep track of my files. Thanks for any feedback you have!

Looks good - I run an almost identical system for my personal photos, using the same programs.

PKGBUILD best practice for autotools and missing required files

I am trying to update one of my packages in the AUR. Upstream using GNU automake/autoconf tools and has worked just fine for previous versions. This time around, the download from upstream is missing several of the mandatory files required by autoconf. I am trying to figure out the best way to deal with this.
1. I can add just create them, and distribute them with the Tarbell, and push them into src directory prior to invoking autoconf.
or
2. I can use the --add-missing flag, but that requires the running of autoconf multiple times (unless I am confused)
What is the best practice when files such as NEWS and README are missing?

I highly recommend you review Brad Hedlund's videos regarding UCS networking here:
http://bradhedlund.com/2010/06/22/cisco-ucs-networking-best-practices/
You may want to focus on Part 10 in particular, as this talks about running UCS in end-host mode without vPC or VSS.
Regards,
Matt

FDM file format best practice

All, We are beginning to implement an Oracle GL and I have been asked to provide input as to the file format provided from the ledger to process through FDM (I know, processing directly into HFM is out..at least for now..).
Is there a "Best Practice" for file formats to load through FDM into HFM. I'm really looking for efficiency (fastest to load, easiest to maintain, etc..)
Yes, we will have to use maps in FDM, so that is part of the consideration.
Questions: Fix or delimited, concatenate fields or not, security, minimize the use of scripts, Is it better to have the GL consolidate etc...?
Thoughts appreciated
Edited by: Wtrdev on Mar 14, 2013 10:02 AM

If possible a Comma or Semi-Colon Delimited File would be easy to maintain and easy to load.
The less use of scripting on the file, the better import performance.

Best practice SOD Library in AACG 8.5.1.278

Hi,
We require best practice SOD Library in AACG 8.5.1.278 for EBS R12. I have searched Oracle edelivery but could only find library for AACG 8.6 . We are using Windows X-64 platform.
Can someone provide a download for the same in English language?
Thanks.
Abhishek Jain

Hi,
The best practice library files will be available in the directory you have downloaded and unzipped the GRC media pack from edelivery. Go to the specific directory in the system / server and select "Content" folder. You can copy the files on to your desktop and upload the same into AACG.
Hope this helps. Let me know if you need any further assistance.
Best Regards,
Manjunath

How to check verison of Best Practice Baseline in existing ECC system?

Hi Expert,
How to check verison of Best Practice Baseline in existing ECC system such as v1.603 or v1.604?
Any help will be appriciate.
Sayan

Dear,
Please go to https://websmp201.sap-ag.de/bestpractices and click on Baseline packages then on right hand side you will see that On which release is SAP Best Practices Baseline package which version is applicable.
If you are on EHP4 then you can use the v1.604.
How to Get SAP Best Practices Data Files for Installation (pdf, 278 KB) please refer this link,
https://websmp201.sap-ag.de/~sapidb/011000358700000421882008E.pdf
Hope it will help you.
Regards,
R.Brahmankar

Folders browsing in Mini Bridge. Best practice

Good morning,
I use Bridge since we have no possibilitiy to see PSD files preview in Photoshop open dialog anymore and pretty satisfied with Bridge functionality.
But Mimi Bridge is different story. For example, I have some dosens of subfolders within main 'Work' folder and usually jump to the right folder simply typing first letters (client name). This works in Bridge but not in Mini Bridge, making the addon useless for me (scrolling is too time consuming for my business).
What is your personal best practice for file browsing in Mini Bridge? Can I switch-on 'browsing through typing' somehow?

What is your personal best practice for file browsing in Mini Bridge? Can I switch-on 'browsing through typing' somehow?
After the first appearance in CS4 (I believe?) it was a promising panel with great possibilities to come. Sadly enough they screwed the next version in a very bad way and never made an effort to repair or develop it further for production user needs and requests (which nowadays seems common practice with Adobe to be frankly).
Your best shot is preparing a collection or a smart collection (with your clients name as search for a complete result) in Bridge itself and navigate to the collection in the folder panel of MB. This avoids to have long waits for cache to build for each new selected folder and multi clicking to find the wanted folder. But as said, that is not the solution you really wanted to hear.
For me first preparing a collection in Bridge with the files I think I need for a project (mostly for a photo album) and then chose this in MB is the only way to make MB working in some way. Combined with creating a new workspace in PS with a floating MB panel (otherwise you can't have multiple rows of thumbs). This is still better then switching between applications but knowing that it could have been so much easier often makes me angry...

Edge Animate Best Practices

Dear Community,
I have been wracking my brain to try to understand why my animation appears constantly jerky. I am new to Edge, and not a coder, and Im wondering why this happens:
http://www.christinaciardullo.com/ESO_HolidayCard_2014_4.html
What am I missing? I wanted to ask some best practices regarding
File Sizes: My pngs generally range from 30-90KB, with larger background images up to 500KB. Is this too much? What are appropriate file sizes for this kind of animation?
Animation Lengths: 2-3 second transitions, and constant back and forth motions.Too much at once?
Overlapping Layers: There is a lot of opacity changing in this - Is it not good to have things animate one on top of the other?
Animating Re-sizing: Maybe this is too much to ask? To zoom out?
Thank You!
C

Based on my experience, zoom-in and outs of large files are generally the number one culprit in performance slowdowns. In your animation, between the zoom-out on the ball and background and the animations on the balls (multiple fade transitions and rotations), there's a lot to process at once. My first couple of suggestions are to decrease the the file size on the background image (the tree) and then to only begin the ball animations once the zoom out has completed. I'm guessing the background image is the 500kb image you referred to. Try taking it down to whatever quality is best before it's noticeably compromised. There's no fast rule for appropriate sizes – much of its depends on what you want to do with it and the platform it's going to run on. For instance, I noticed that the animation runs smoothly in Chrome while it has the hardest time in Firefox.

Best Practice EPA files...

Similar Messages

Maybe you are looking for