Search Results

Found 20 repositories(showing 20)

10-things-linux

carltheperson

🧡51

Getting better at Linux with 10 mini-projects.

342

MIT

Updated 1 month ago

Its a automatic PAYLOAD injector tools for kali linux powered by LogOut AKA Ethical Hacker. ##First os all make install of all the files required during this process . you can directly do it by installation script i.e. install.sh on the main folder. Run ./install.sh OR install the following packages 1. metasploit-framework 2. Android Debug Bridge(ADB) 3. Fastboot 4. colorama for python 5. Python3 Be sure to setup or place the HacksByLogout folder on root directory of system and not to touch or edit any files or it may cause you to stop working. Steps You need to follow!!!! (1) Just enter your IP of device. Note: you can check your ip using ifconfig command in terminal. (2) Enter the port : Note: I usually recommend using 8080, 4444, 5555 or any 4 digit number as a port since it is very necessary, you need to use the port . (3) turn on usb debugging on your device and plug it for 10 seconds. Time depend upon your internet connection and system power. (4) After the injection , it will automatic open msf console so that it will be easy for you. (5) type the commands given to you on opened terminal. After exploit just tap or launch the installed PAYLOAD for single time and you will be connected. MAKING PAYLOAD SECURE!!! after connection just type the following command and hit enter. hide_app_icon this let you to hide your PAYLOAD and make it undetectable by user. use help command to list the things you can do. Copyright@HacksByLogOut

Python

Updated 3 months ago

Window

Buildsoftwaresphere

❤️25

Updated 6 months ago

Install-OpenProject-Project-Managmen-Software-local-servert

naimul3070

❤️30

Opensource for universities, educational institutions, research, IT / technology companies, NGOs, administrations, foundations, public institutions, authorities, banks and insurance companies, and the automotive industry. The platform offers project planning and visualization, application management, release planning, product management, team collaboration, task management, bug tracking, and budget planning. With this open-source solution, the users can record all processes in one central location, create product roadmaps, record all processes in one central location; create project templates; use widgets to visualize project status and progress; create detailed release planning, share the information with team and collect feedback from customers and employees. Apart from this Gantt charts/timeline management; custom fields for work packages; meetings management; scrum (backlogs and task board); calendar, time tracking, cost reporting, budgeting, bug tracking, wiki; twp-factor authentication, and more are some other features community edition offers. In Premium functions, OpenProject includes agile boards, logo and color schemes, your own design and logo, user-defined fields, single sign-on, individual help texts, highlighting of attributes, and more. One can get a complete function comparison amidst three versions, on the official page of this project. Contents [show] Steps to install OpenProject in Ubuntu 20.04 LTS Linux server 1. Add PGP Key The packages to install OpenProject are not available directly using the base repository of Ubuntu 20.04, hence we have to add a repository provided by the developers of this software platform. Well, but the system always needs to ensure that the packages it is getting are authentic and coming only from the source of repository added for it. And for that, we need to add the PGP key used to sign the OpenProject packages. Copy Me wget -qO- https://dl.packager.io/srv/opf/openproject/key | sudo apt-key add - GPG key for OpenProject 2. Integrate OpenProject repository in Ubuntu 20.04 As I mentioned above that we need to add manually a repository to get the OpenProject packages for installation, therefore, for that run the following given command: Copy-Past whole block of given command: Copy Me sudo wget -O /etc/apt/sources.list.d/openproject.list https://dl.packager.io/srv/opf/openproject/stable/12/installer/ubuntu/20.04.repo Add openproject repository on Ubuntu 20.04 3. Run system update To let the system know we have added a new repository to get a third-party application, run once the system update command: Copy Me sudo apt update 4. Command to install OpenProject in Ubuntu 20.04 LTS Finally, all the key things we require to get the OpenProject have been set, it’s time to use the APT package manager to start the installation process. Copy Me sudo apt install openproject sudo apt install openproject ubuntu 20.04 linux server 5. Start configuring OpenProject Well, the installation has been completed but yet has to be configured to get its web interface up and running. To start the further configuration run the given command: Copy Me sudo openproject configure Select Default OpenProject Users from the Construction field can go for the BIM one. default openproject BIM 6. Configure PostgreSQL To store its data we need a database server, here the OpenProject offers you an option to automatically install “Postgres“, however, if you already have an installed Postgres somewhere or on the same server then you can go for “Use an existing PostgreSQL database” option. However, here we are going for “Install a new PostgreSQL server and database locally“. Select it, Okay, and then hit the Enter key. PostgreSQL Auto Install for OpenProject 7. Install Apache Webserver Next, we need a webserver to serve web pages of OpenProject over a network. Hence, the installation wizard will let you install the Apache webserver if it is not already. install apache2 server Set Fully Qualified domain To access the OpenProject using FQDN, mention the same here. For example, here we are using demo.how2shout.com. You can use whatever you have. Alternatively, if you want to access it using a server IP address then mention that instead of a domain name. set fully qualified domain for OpenProject on Ubuntu Server Path (optional) This is optional. If you want to access your OpenProject web interface under some folder then you can mention it here. For example, let say you already have some website running on your server and to access it you are using your root domain then we cannot use the same domain to access another web platform. Therefore, to solve we can install another website under a subfolder. And the name of that subfolder you can mention here. server path prefix 8. Server SSL Those who already have SSL for the domain they want to use with OpenProject, do not need to install a new SSL certificate, even the ones who are using either Let’s Encrypt or Cloudflare. However, if you don’t have any existing SSL certificate then of course go for the Yes option otherwise NO. Server SSL for Project management Application 9. Install Subversion Just select the “Install Subversion repository support”. Subversion support Again hit the Enter key to set the default path and then install Git repository support, if you want. 10. STMP for Sending Emails Users who want to send emails to others from the web interface of OpenProject need to configure either SendMail or SMTP. We recommend using SMTP to route mail through your mail servers. Select it and configure the same. Or else just SKIP who don’t require emails service, right now. Next, select to install Memcache server for better cache performance or just skip if you don’t need it. Install a new memcached server Wait for a few minutes and the OpenProject open source project management will be on your server. 11. Access OpenProject Web interface Once the installation is completed, it’s time to access the Web interface of OpenProject to start managing our project through it. So, open any web browser on your local system that can access the server IP address where OpenProject is installed. In the URL either type the server IP address or Fully Qualified domain name associated with it. http://server-ip-address or http://your-domain.com If you have installed the OpenProject not in the root directory and with some server suffix or in simple words mentioned the folder name you have assigned during the installation of this project management platform. example: http://server-ip-address/your-sub-folder or http://your-domain.com/your-sub-foler Note: Replace- your-domain. com with the Domain you have added to use with OpenProject while configuring it. Whereas the sub-folder is the Server path suffix if you have mentioned while setting it up. Dashboard of project management Linux 12. Sign-in or Login OpenProject backend Now, let’s log in to the backend. The default username is admin and the password is also admin. Login openProject Backend Admin Change the default Admin password to something strong. Change Admin User 13. Admin Dashboard Finally, you have successfully installed the OpenProject on your Ubuntu 20.04 LTS Linux. Now you can start going through its learning curves to efficiently manage your projects. For more information once can visit its documentation page. OpenProject Installed in Ubuntu 20.04 Linux 14. Video Tutorial Video Player 00:00 14:15 Other Articles: • Top 3 Command Line Ubuntu Package Manager tools • How to install Gparted on Ubuntu 20.04 LTS • How to install Bitwarden server on Ubuntu 20.04 • Install VNC Server on Ubuntu 20.04 | 18.04 RELATED POSTS DaloRADIUS and FreeRADIUS install on Ubuntu 20.04 serverHeyan Maurya UBUNTUInstall FreeRadius & web GUI daloRADIUS on Ubuntu 20.04 serverSet Default Kernel Version of UbuntuHeyan Maurya UBUNTUHow to change default kernel in Ubuntu 22.04 | 20.04 LTSWSL Ubuntu 22.04 LTS Jammy Jelly FIshHeyan Maurya UBUNTUHow to Upgrade WSL 2 or 1 Ubuntu 20.04 to 22.04 LTSGoogle Drive in Ubuntu 20.04 LTSHeyan Maurya UBUNTU4153 VIEWSHow to Setup and use Google Drive on Ubuntu 20.04 LEAVE A REPLY Comment Text* Name* Email* Website Save my name, email, and website in this browser for the next time I comment. This site uses Akismet to reduce spam. Learn how your comment data is processed.

Updated 7 months ago

CS344-OSI---Assignment-3-Small-Shell

thehuy2000

❤️35

In this assignment you will write smallsh your own shell in C. smallsh will implement a subset of features of well-known shells, such as bash. Your program will Provide a prompt for running commands Handle blank lines and comments, which are lines beginning with the # character Provide expansion for the variable $$ Execute 3 commands exit, cd, and status via code built into the shell Execute other commands by creating new processes using a function from the exec family of functions Support input and output redirection Support running commands in foreground and background processes Implement custom handlers for 2 signals, SIGINT and SIGTSTP Learning Outcomes After successful completion of this assignment, you should be able to do the following Describe the Unix process API (Module 4, MLO 2) Write programs using the Unix process API (Module 4, MLO 3) Explain the concept of signals and their uses (Module 5, MLO 2) Write programs using the Unix API for signal handling (Module 5, MLO 3) Explain I/O redirection and write programs that can employ I/O redirection (Module 5, MLO 4) Program Functionality 1. The Command Prompt Use the colon : symbol as a prompt for each command line. The general syntax of a command line is: command [arg1 arg2 ...] [< input_file] [> output_file] [&] …where items in square brackets are optional. You can assume that a command is made up of words separated by spaces. The special symbols <, > and & are recognized, but they must be surrounded by spaces like other words. If the command is to be executed in the background, the last word must be &. If the & character appears anywhere else, just treat it as normal text. If standard input or output is to be redirected, the > or < words followed by a filename word must appear after all the arguments. Input redirection can appear before or after output redirection. Your shell does not need to support any quoting; so arguments with spaces inside them are not possible. We are also not implementing the pipe "|" operator. Your shell must support command lines with a maximum length of 2048 characters, and a maximum of 512 arguments. You do not need to do any error checking on the syntax of the command line. 2. Comments & Blank Lines Your shell should allow blank lines and comments. Any line that begins with the # character is a comment line and should be ignored. Mid-line comments, such as the C-style //, will not be supported. A blank line (one without any commands) should also do nothing. Your shell should just re-prompt for another command when it receives either a blank line or a comment line. 3. Expansion of Variable $$ Your program must expand any instance of "$$" in a command into the process ID of the smallsh itself. Your shell does not otherwise perform variable expansion. 4. Built-in Commands Your shell will support three built-in commands: exit, cd, and status. These three built-in commands are the only ones that your shell will handle itself - all others are simply passed on to a member of the exec() family of functions. You do not have to support input/output redirection for these built in commands These commands do not have to set any exit status. If the user tries to run one of these built-in commands in the background with the & option, ignore that option and run the command in the foreground anyway (i.e. don't display an error, just run the command in the foreground). exit The exit command exits your shell. It takes no arguments. When this command is run, your shell must kill any other processes or jobs that your shell has started before it terminates itself. cd The cd command changes the working directory of smallsh. By itself - with no arguments - it changes to the directory specified in the HOME environment variable This is typically not the location where smallsh was executed from, unless your shell executable is located in the HOME directory, in which case these are the same. This command can also take one argument: the path of a directory to change to. Your cd command should support both absolute and relative paths. status The status command prints out either the exit status or the terminating signal of the last foreground process ran by your shell. If this command is run before any foreground command is run, then it should simply return the exit status 0. The three built-in shell commands do not count as foreground processes for the purposes of this built-in command - i.e., status should ignore built-in commands. 5. Executing Other Commands Your shell will execute any commands other than the 3 built-in command by using fork(), exec() and waitpid() Whenever a non-built in command is received, the parent (i.e., smallsh) will fork off a child. The child will use a function from the exec() family of functions to run the command. Your shell should use the PATH variable to look for non-built in commands, and it should allow shell scripts to be executed If a command fails because the shell could not find the command to run, then the shell will print an error message and set the exit status to 1 A child process must terminate after running a command (whether the command is successful or it fails). 6. Input & Output Redirection You must do any input and/or output redirection using dup2(). The redirection must be done before using exec() to run the command. An input file redirected via stdin should be opened for reading only; if your shell cannot open the file for reading, it should print an error message and set the exit status to 1 (but don't exit the shell). Similarly, an output file redirected via stdout should be opened for writing only; it should be truncated if it already exists or created if it does not exist. If your shell cannot open the output file it should print an error message and set the exit status to 1 (but don't exit the shell). Both stdin and stdout for a command can be redirected at the same time (see example below). 7. Executing Commands in Foreground & Background Foreground Commands Any command without an & at the end must be run as a foreground command and the shell must wait for the completion of the command before prompting for the next command. For such commands, the parent shell does NOT return command line access and control to the user until the child terminates. Background Commands Any non built-in command with an & at the end must be run as a background command and the shell must not wait for such a command to complete. For such commands, the parent must return command line access and control to the user immediately after forking off the child. The shell will print the process id of a background process when it begins. When a background process terminates, a message showing the process id and exit status will be printed. This message must be printed just before the prompt for a new command is displayed. If the user doesn't redirect the standard input for a background command, then standard input should be redirected to /dev/null If the user doesn't redirect the standard output for a background command, then standard output should be redirected to /dev/null 8. Signals SIGINT & SIGTSTP SIGINT A CTRL-C command from the keyboard sends a SIGINT signal to the parent process and all children at the same time (this is a built-in part of Linux). Your shell, i.e., the parent process, must ignore SIGINT Any children running as background processes must ignore SIGINT A child running as a foreground process must terminate itself when it receives SIGINT The parent must not attempt to terminate the foreground child process; instead the foreground child (if any) must terminate itself on receipt of this signal. If a child foreground process is killed by a signal, the parent must immediately print out the number of the signal that killed it's foreground child process (see the example) before prompting the user for the next command. SIGTSTP A CTRL-Z command from the keyboard sends a SIGTSTP signal to your parent shell process and all children at the same time (this is a built-in part of Linux). A child, if any, running as a foreground process must ignore SIGTSTP. Any children running as background process must ignore SIGTSTP. When the parent process running the shell receives SIGTSTP The shell must display an informative message (see below) immediately if it's sitting at the prompt, or immediately after any currently running foreground process has terminated The shell then enters a state where subsequent commands can no longer be run in the background. In this state, the & operator should simply be ignored, i.e., all such commands are run as if they were foreground processes. If the user sends SIGTSTP again, then your shell will Display another informative message (see below) immediately after any currently running foreground process terminates The shell then returns back to the normal condition where the & operator is once again honored for subsequent commands, allowing them to be executed in the background. See the example below for usage and the exact syntax which you must use for these two informative messages. Sample Program Execution Here is an example run using smallsh. Note that CTRL-C has no effect towards the bottom of the example, when it's used while sitting at the command prompt: $ smallsh : ls junk smallsh smallsh.c : ls > junk : status exit value 0 : cat junk junk smallsh smallsh.c : wc < junk > junk2 : wc < junk 3 3 23 : test -f badfile : status exit value 1 : wc < badfile cannot open badfile for input : status exit value 1 : badfile badfile: no such file or directory : sleep 5 ^Cterminated by signal 2 : status & terminated by signal 2 : sleep 15 & background pid is 4923 : ps PID TTY TIME CMD 4923 pts/0 00:00:00 sleep 4564 pts/0 00:00:03 bash 4867 pts/0 00:01:32 smallsh 4927 pts/0 00:00:00 ps : : # that was a blank command line, this is a comment line : background pid 4923 is done: exit value 0 : # the background sleep finally finished : sleep 30 & background pid is 4941 : kill -15 4941 background pid 4941 is done: terminated by signal 15 : pwd /nfs/stak/users/chaudhrn/CS344/prog3 : cd : pwd /nfs/stak/users/chaudhrn : cd CS344 : pwd /nfs/stak/users/chaudhrn/CS344 : echo 4867 4867 : echo $$ 4867 : ^C^Z Entering foreground-only mode (& is now ignored) : date Mon Jan 2 11:24:33 PST 2017 : sleep 5 & : date Mon Jan 2 11:24:38 PST 2017 : ^Z Exiting foreground-only mode : date Mon Jan 2 11:24:39 PST 2017 : sleep 5 & background pid is 4963 : date Mon Jan 2 11:24:39 PST 2017 : exit $ Hints & Resources 1. The Command Prompt Be sure you flush out the output buffers each time you print, as the text that you're outputting may not reach the screen until you do in this kind of interactive program. To do this, call fflush() immediately after each and every time you output text. Consider defining a struct in which you can store all the different elements included in a command. Then as you parse a command, you can set the value of members of a variable of this struct type. 2. Comments & Blank Lines This should be simple. 3. Expansion of Variable $$ Here are examples to illustrate the required behavior. Suppose the process ID of smallsh is 179. Then The string foo$$$$ in the command is converted to foo179179 The string foo$$$ in the command is converted to foo179$ 4. Built-in Commands It is recommended that you program the built-in commands first, before tackling the commands that require fork(), exec() and waitpid(). The built-in commands don't set the value of status. This means that however you are keeping track of the status, don't change it after the execution of a built-in command. A process can use chdir() (Links to an external site.) to change its directory. To test the implementation of the cd command in smallsh, don't use getenv("PWD") because it will not give you the correct result. Instead, you can use the function getcwd() (Links to an external site.). Here is why getenv("PWD") doesn't give you the correct result: PWD is an environment variable. As discussed in Module 4, Exploration: Environment "When a parent process forks a child process, the child process inherits the environment of its parent process." When you run smallsh from a bash shell, smallsh inherits the environment of this bash shell The value of PWD in the bash shell is set to the directory in which you are when you run the command to start smallsh smallsh inherits this value of PWD. When you change the directory in smallsh, it doesn't update the value of the environment variable PWD 5. Executing Other Commands Note that if exec() is told to execute something that it cannot do, like run a program that doesn't exist, it will fail, and return the reason why. In this case, your shell should indicate to the user that a command could not be executed (which you know because exec() returned an error), and set the value retrieved by the built-in status command to 1. Make sure that the child process that has had an exec() call fail terminates itself, or else it often loops back up to the top and tries to become a parent shell. This is easy to spot: if the output of the grading script seems to be repeating itself, then you've likely got a child process that didn't terminate after a failed exec(). You can choose any function in the exec() family. However, we suggest that using either execlp() or execvp() will be simplest because of the following reasons smallsh doesn't need to pass a new environment to the program. So the additional functionality provided by the exec() functions with names ending in e is not required. One example of a command that smallsh needs to run is ls (the graders will try this command at the start of the testing). Running this command will be a lot easier using the exec() functions that search the PATH environment variable. 6. Input & Output Redirection We recommend that the needed input/output redirection should be done in the child process. Note that after using dup2() to set up the redirection, the redirection symbol and redirection destination/source are NOT passed into the exec command For example, if the command given is ls > junk, then you handle the redirection to "junk" with dup2() and then simply pass ls into exec(). 7. Executing Commands in Foreground & Background Foreground Commands For a foreground command, it is recommend to have the parent simply call waitpid() on the child, while it waits. Background Commands The shell should respect the input and output redirection operators for a command regardless of whether the command is to be run in the foreground or the background. This means that a background command should use /dev/null for input only when input redirection is not specified in the command. Similarly a background command should use /dev/null for output only when output redirection is not specified in the command. Your parent shell will need to periodically check for the background child processes to complete, so that they can be cleaned up, as the shell continues to run and process commands. Consider storing the PIDs of non-completed background processes in an array. Then every time BEFORE returning access to the command line to the user, you can check the status of these processes using waitpid(...NOHANG...). Alternatively, you may use a signal handler to immediately wait() for child processes that terminate, as opposed to periodically checking a list of started background processes The time to print out when these background processes have completed is just BEFORE command line access and control are returned to the user, every time that happens. 8. Signals SIGINT & SIGTSTP Reentrancy is important when we consider that signal handlers cause jumps in execution that cause problems with certain functions. Note that the printf() family of functions is NOT reentrant. In your signal handlers, when outputting text, you must use other output functions! What to turn in? You can only use C for coding this assignment and you must use the gcc compiler. You can use C99 or GNU99 standard or the default standard used by the gcc installation on os1. Your assignment will be graded on os1. Submit a single zip file with all your code, which can be in as many different files as you want. This zip file must be named youronid_program3.zip where youronid should be replaced by your own ONID. E.g., if chaudhrn was submitting the assignment, the file must be named chaudhrn_program3.zip. In the zip file, you must include a text file called README.txt that contains instructions on how to compile your code using gcc to create an executable file that must be named smallsh. Your zip file should not contain any extraneous files. In particular, make sure not to zip up the __MACOSX directories. When you resubmit a file in Canvas, Canvas can attach a suffix to the file, e.g., the file name may become chaudhrn_program3-1.zip. Don't worry about this name change as no points will be deducted because of this. Caution During the development of this program, take extra care to only do your work on os1, our class server, as your software will likely negatively impact whatever machine it runs on, especially before it is finished. If you cause trouble on one of the non-class, public servers, it could hurt your grade! If you are having trouble logging in to any of our EECS servers because of runaway processes, please use this page to kill off any programs running on your account that might be blocking your access: T.E.A.C.H. - The Engineering Accounts and Classes HomepageLinks to an external site. Grading Criteria This assignment is worth 20% of your grade and there are 180 points available for it. 170 points are available in the test script, while the final 10 points will be based on your style, readability, and commenting. Comment well, often, and verbosely: we want to see that you are telling us WHY you are doing things, in addition to telling us WHAT you are doing. Once the program is compiled, according to your specifications given in README.txt, your shell will be executed to run a few sample commands against (ls, status, exit, in that order). If the program does not successfully work on those commands, it will receive a zero. If it works, then the grading script will be run against it (as detailed below) for final grading. Points will be assigned according to the grading script running on our class server only. Grading Method Here is the grading script p3testscript. It is a bash script that starts the smallsh program and runs commands on smallsh's command line. Most of the commands run by the grading script are very similar to the commands shown in the section Sample Program Execution. You can open the script in a text editor. The comments in the script will show you the points for individual items. Use the script to prepare for your grade, as this is how it's being earned. To run the script, place it in the same directory as your compiled shell, chmod it (chmod +x ./p3testscript) and run this command from a bash prompt: $ ./p3testscript 2>&1 or $ ./p3testscript 2>&1 | more or $ ./p3testscript > mytestresults 2>&1 Do not worry if the spacing, indentation, or look of the output of the script is different than when you run it interactively: that won’t affect your grade. The script may add extra colons at the beginning of lines or do other weird things, like put output about terminating processes further down the script than you intended. If your program does not work with the grading script, and you instead request that we grade your script by hand, we will apply a 15% reduction to your final score. So from the very beginning, make sure that you work with the grading script on our class server!

Updated 6 months ago

10-things-to-do-AFTER-Installing-DEBIAN-LINUX

MinersWin

❤️35

Are you looking for things to do after installing Debian? These 10 things to do after installing Debian 9 will help you make your Debian desktop experience better.

Updated 8 months ago

CS344-OSI---Assignment-3-Small-Shell

JoshBell302

🧡65

Updated 1 hour ago

CouseraDatasharing

AdekoyaOlatolokikiAyomide

❤️35

How to share data with a statistician This is a guide for anyone who needs to share data with a statistician or data scientist. The target audiences I have in mind are: Collaborators who need statisticians or data scientists to analyze data for them Students or postdocs in various disciplines looking for consulting advice Junior statistics students whose job it is to collate/clean/wrangle data sets The goals of this guide are to provide some instruction on the best way to share data to avoid the most common pitfalls and sources of delay in the transition from data collection to data analysis. The Leek group works with a large number of collaborators and the number one source of variation in the speed to results is the status of the data when they arrive at the Leek group. Based on my conversations with other statisticians this is true nearly universally. My strong feeling is that statisticians should be able to handle the data in whatever state they arrive. It is important to see the raw data, understand the steps in the processing pipeline, and be able to incorporate hidden sources of variability in one's data analysis. On the other hand, for many data types, the processing steps are well documented and standardized. So the work of converting the data from raw form to directly analyzable form can be performed before calling on a statistician. This can dramatically speed the turnaround time, since the statistician doesn't have to work through all the pre-processing steps first. What you should deliver to the statistician To facilitate the most efficient and timely analysis this is the information you should pass to a statistician: The raw data. A tidy data set A code book describing each variable and its values in the tidy data set. An explicit and exact recipe you used to go from 1 -> 2,3 Let's look at each part of the data package you will transfer. The raw data It is critical that you include the rawest form of the data that you have access to. This ensures that data provenance can be maintained throughout the workflow. Here are some examples of the raw form of data: The strange binary file your measurement machine spits out The unformatted Excel file with 10 worksheets the company you contracted with sent you The complicated JSON data you got from scraping the Twitter API The hand-entered numbers you collected looking through a microscope You know the raw data are in the right format if you: Ran no software on the data Did not modify any of the data values You did not remove any data from the data set You did not summarize the data in any way If you made any modifications of the raw data it is not the raw form of the data. Reporting modified data as raw data is a very common way to slow down the analysis process, since the analyst will often have to do a forensic study of your data to figure out why the raw data looks weird. (Also imagine what would happen if new data arrived?) The tidy data set The general principles of tidy data are laid out by Hadley Wickham in this paper and this video. While both the paper and the video describe tidy data using R, the principles are more generally applicable: Each variable you measure should be in one column Each different observation of that variable should be in a different row There should be one table for each "kind" of variable If you have multiple tables, they should include a column in the table that allows them to be joined or merged While these are the hard and fast rules, there are a number of other things that will make your data set much easier to handle. First is to include a row at the top of each data table/spreadsheet that contains full row names. So if you measured age at diagnosis for patients, you would head that column with the name AgeAtDiagnosis instead of something like ADx or another abbreviation that may be hard for another person to understand. Here is an example of how this would work from genomics. Suppose that for 20 people you have collected gene expression measurements with RNA-sequencing. You have also collected demographic and clinical information about the patients including their age, treatment, and diagnosis. You would have one table/spreadsheet that contains the clinical/demographic information. It would have four columns (patient id, age, treatment, diagnosis) and 21 rows (a row with variable names, then one row for every patient). You would also have one spreadsheet for the summarized genomic data. Usually this type of data is summarized at the level of the number of counts per exon. Suppose you have 100,000 exons, then you would have a table/spreadsheet that had 21 rows (a row for gene names, and one row for each patient) and 100,001 columns (one row for patient ids and one row for each data type). If you are sharing your data with the collaborator in Excel, the tidy data should be in one Excel file per table. They should not have multiple worksheets, no macros should be applied to the data, and no columns/cells should be highlighted. Alternatively share the data in a CSV or TAB-delimited text file. (Beware however that reading CSV files into Excel can sometimes lead to non-reproducible handling of date and time variables.) The code book For almost any data set, the measurements you calculate will need to be described in more detail than you can or should sneak into the spreadsheet. The code book contains this information. At minimum it should contain: Information about the variables (including units!) in the data set not contained in the tidy data Information about the summary choices you made Information about the experimental study design you used In our genomics example, the analyst would want to know what the unit of measurement for each clinical/demographic variable is (age in years, treatment by name/dose, level of diagnosis and how heterogeneous). They would also want to know how you picked the exons you used for summarizing the genomic data (UCSC/Ensembl, etc.). They would also want to know any other information about how you did the data collection/study design. For example, are these the first 20 patients that walked into the clinic? Are they 20 highly selected patients by some characteristic like age? Are they randomized to treatments? A common format for this document is a Word file. There should be a section called "Study design" that has a thorough description of how you collected the data. There is a section called "Code book" that describes each variable and its units. How to code variables When you put variables into a spreadsheet there are several main categories you will run into depending on their data type: Continuous Ordinal Categorical Missing Censored Continuous variables are anything measured on a quantitative scale that could be any fractional number. An example would be something like weight measured in kg. Ordinal data are data that have a fixed, small (< 100) number of levels but are ordered. This could be for example survey responses where the choices are: poor, fair, good. Categorical data are data where there are multiple categories, but they aren't ordered. One example would be sex: male or female. This coding is attractive because it is self-documenting. Missing data are data that are unobserved and you don't know the mechanism. You should code missing values as NA. Censored data are data where you know the missingness mechanism on some level. Common examples are a measurement being below a detection limit or a patient being lost to follow-up. They should also be coded as NA when you don't have the data. But you should also add a new column to your tidy data called, "VariableNameCensored" which should have values of TRUE if censored and FALSE if not. In the code book you should explain why those values are missing. It is absolutely critical to report to the analyst if there is a reason you know about that some of the data are missing. You should also not impute/make up/ throw away missing observations. In general, try to avoid coding categorical or ordinal variables as numbers. When you enter the value for sex in the tidy data, it should be "male" or "female". The ordinal values in the data set should be "poor", "fair", and "good" not 1, 2 ,3. This will avoid potential mixups about which direction effects go and will help identify coding errors. Always encode every piece of information about your observations using text. For example, if you are storing data in Excel and use a form of colored text or cell background formatting to indicate information about an observation ("red variable entries were observed in experiment 1.") then this information will not be exported (and will be lost!) when the data is exported as raw text. Every piece of data should be encoded as actual text that can be exported. The instruction list/script You may have heard this before, but reproducibility is a big deal in computational science. That means, when you submit your paper, the reviewers and the rest of the world should be able to exactly replicate the analyses from raw data all the way to final results. If you are trying to be efficient, you will likely perform some summarization/data analysis steps before the data can be considered tidy. The ideal thing for you to do when performing summarization is to create a computer script (in R, Python, or something else) that takes the raw data as input and produces the tidy data you are sharing as output. You can try running your script a couple of times and see if the code produces the same output. In many cases, the person who collected the data has incentive to make it tidy for a statistician to speed the process of collaboration. They may not know how to code in a scripting language. In that case, what you should provide the statistician is something called pseudocode. It should look something like: Step 1 - take the raw file, run version 3.1.2 of summarize software with parameters a=1, b=2, c=3 Step 2 - run the software separately for each sample Step 3 - take column three of outputfile.out for each sample and that is the corresponding row in the output data set You should also include information about which system (Mac/Windows/Linux) you used the software on and whether you tried it more than once to confirm it gave the same results. Ideally, you will run this by a fellow student/labmate to confirm that they can obtain the same output file you did. What you should expect from the analyst When you turn over a properly tidied data set it dramatically decreases the workload on the statistician. So hopefully they will get back to you much sooner. But most careful statisticians will check your recipe, ask questions about steps you performed, and try to confirm that they can obtain the same tidy data that you did with, at minimum, spot checks. You should then expect from the statistician: An analysis script that performs each of the analyses (not just instructions) The exact computer code they used to run the analysis All output files/figures they generated. This is the information you will use in the supplement to establish reproducibility and precision of your results. Each of the steps in the analysis should be clearly explained and you should ask questions when you don't understand what the analyst did. It is the responsibility of both the statistician and the scientist to understand the statistical analysis. You may not be able to perform the exact analyses without the statistician's code, but you should be able to explain why the statistician performed each step to a labmate/your principal investigator. Contributors Jeff Leek - Wrote the initial version. L. Collado-Torres - Fixed typos, added links. Nick Reich - Added tips on storing data as text. Nick Horton - Minor wording suggestions.

Updated 1 year ago

Bluetooth-Support-for-HP-14-Chromebook-Chroot

tacticalafro

❤️40

Let me start off by saying that I am a noob at all of this. I just threw crouton on my HP 14 Chromebook ($349 version with Haswell processor) and am currently dual-booting Linux 13.10. For some reason I am completely unable to use bluetooth on the Linux side of things...even though it works fine on Chrome OS. Thoughts/guidance/help?

Updated 4 weeks ago

nemesis-current

adouble42

❤️25

nemesis is an actively developed (hey, i'm still here, and i'll be more visibly so again soon, wrapping some other things up) freebsd, debian linux and Mac OS X (tested through 10.11) port based on TrueCrypt. right now it is largely truecrypt code, but per the license, it's not truecrypt.

NOASSERTION

C++

Updated 9 years ago

w

cbool

❤️35

############################################### # Trinity Core Auth Server configuration file # ############################################### [authserver] ################################################################################################### # SECTION INDEX # # EXAMPLE CONFIG # AUTH SERVER SETTINGS # MYSQL SETTINGS # LOGGING SYSTEM SETTINGS # ################################################################################################### ################################################################################################### # EXAMPLE CONFIG # # Variable # Description: Brief description what the variable is doing. # Important: Annotation for important things about this variable. # Example: "Example, i.e. if the value is a string" # Default: 10 - (Enabled|Comment|Variable name in case of grouped config options) # 0 - (Disabled|Comment|Variable name in case of grouped config options) # # Note to developers: # - Copy this example to keep the formatting. # - Line breaks should be at column 100. ################################################################################################### ################################################################################################### # AUTH SERVER SETTINGS # # LogsDir # Description: Logs directory setting. # Important: LogsDir needs to be quoted, as the string might contain space characters. # Logs directory must exists, or log file creation will be disabled. # Default: "" - (Log files will be stored in the current path) LogsDir = "Logs" # # MaxPingTime # Description: Time (in minutes) between database pings. # Default: 30 MaxPingTime = 30 # # RealmServerPort # Description: TCP port to reach the auth server. # Default: 3724 RealmServerPort = 3724 # # # BindIP # Description: Bind auth server to IP/hostname # Default: "0.0.0.0" - (Bind to all IPs on the system) BindIP = "0.0.0.0" # # PidFile # Description: Auth server PID file. # Example: "./authserver.pid" - (Enabled) # Default: "" - (Disabled) PidFile = "" # # UseProcessors # Description: Processors mask for Windows based multi-processor systems. # Default: 0 - (Selected by OS) # 1+ - (Bit mask value of selected processors) UseProcessors = 0 # # ProcessPriority # Description: Process priority setting for Windows based systems. # Default: 1 - (High) # 0 - (Normal) ProcessPriority = 1 # # RealmsStateUpdateDelay # Description: Time (in seconds) between realm list updates. # Default: 20 - (Enabled) # 0 - (Disabled) RealmsStateUpdateDelay = 20 # # WrongPass.MaxCount # Description: Number of login attemps with wrong password before the account or IP will be # banned. # Default: 0 - (Disabled) # 1+ - (Enabled) WrongPass.MaxCount = 0 # # WrongPass.BanTime # Description: Time (in seconds) for banning account or IP for invalid login attempts. # Default: 600 - (10 minutes) # 0 - (Permanent ban) WrongPass.BanTime = 600 # # WrongPass.BanType # Description: Ban type for invalid login attempts. # Default: 0 - (Ban IP) # 1 - (Ban Account) WrongPass.BanType = 0 # ################################################################################################### ################################################################################################### # MYSQL SETTINGS # # LoginDatabaseInfo # Description: Database connection settings for the realm server. # Example: "hostname;port;username;password;database" # ".;somenumber;username;password;database" - (Use named pipes on Windows # "enable-named-pipe" to [mysqld] # section my.ini) # ".;/path/to/unix_socket;username;password;database" - (use Unix sockets on # Unix/Linux) # Default: "127.0.0.1;3306;trinity;trinity;auth" LoginDatabaseInfo = "127.0.0.1;3316;root;trinity;realmd" # # LoginDatabase.WorkerThreads # Description: The amount of worker threads spawned to handle asynchronous (delayed) MySQL # statements. Each worker thread is mirrored with its own connection to the # Default: 1 LoginDatabase.WorkerThreads = 1 # ################################################################################################### ################################################################################################### # # LOGGING SYSTEM SETTINGS # # Appender config values: Given a appender "name" # Appender.name # Description: Defines 'where to log' # Format: Type,LogLevel,Flags,optional1,optional2,optional3 # # Type # 0 - (None) # 1 - (Console) # 2 - (File) # 3 - (DB) # # LogLevel # 0 - (Disabled) # 1 - (Trace) # 2 - (Debug) # 3 - (Info) # 4 - (Warn) # 5 - (Error) # 6 - (Fatal) # # Flags: # 0 - None # 1 - Prefix Timestamp to the text # 2 - Prefix Log Level to the text # 4 - Prefix Log Filter type to the text # 8 - Append timestamp to the log file name. Format: YYYY-MM-DD_HH-MM-SS (Only used with Type = 2) # 16 - Make a backup of existing file before overwrite (Only used with Mode = w) # # Colors (read as optional1 if Type = Console) # Format: "fatal error warn info debug trace" # 0 - BLACK # 1 - RED # 2 - GREEN # 3 - BROWN # 4 - BLUE # 5 - MAGENTA # 6 - CYAN # 7 - GREY # 8 - YELLOW # 9 - LRED # 10 - LGREEN # 11 - LBLUE # 12 - LMAGENTA # 13 - LCYAN # 14 - WHITE # Example: "13 11 9 5 3 1" # # File: Name of the file (read as optional1 if Type = File) # Allows to use one "%s" to create dynamic files # # Mode: Mode to open the file (read as optional2 if Type = File) # a - (Append) # w - (Overwrite) # # MaxFileSize: Maximum file size of the log file before creating a new log file # (read as optional3 if Type = File) # Size is measured in bytes expressed in a 64-bit unsigned integer. # Maximum value is 4294967295 (4 gb). Leave blank for no limit. # NOTE: Does not work with dynamic filenames. # Example: 536870912 (512 mb) # Appender.Console=1,2,0 Appender.Auth=2,2,0,Auth.log,w # LogLevel # 0 - (Disabled) # 1 - (Trace) # 2 - (Debug) # 3 - (Info) # 4 - (Warn) # 5 - (Error) # 6 - (Fatal) # # AppenderList: List of appenders linked to logger # (Using spaces as separator). # # Appenders # Description: List of Appenders to read from config # (Using spaces as separator). # Default: "Console Server" Appenders=Console Auth # Logger config values: Given a logger "name" # Logger.name # Description: Defines 'What to log' # Format: Type,LogLevel,AppenderList # Type # 0 - Default. Each type that has no config will # rely on this one. Core will create this logger # (disabled) if it's not configured # 7 - Network input/output, # 30 - Authserver Logger.Root=0,3,Console Auth # # Loggers # Description: List of Loggers to read from config # (Using spaces as separator). # Default: "root" Loggers=Root # ###################################################################################################

Updated 1 year ago

10-things-linux

kirohi-dev

❤️25

No description available

Updated 5 years ago

10-things-linux

Shashank-Handa

❤️35

10 mini projects with linux to learn linux and Operating systems in general better

C++

Updated 1 year ago

RedHat-Enterprise-Linux-10-Post-Install-Guide

Miras1990

❤️45

Things to do after installing RedHat Enterprise Linux 10

Updated 1 month ago

The-Top-10-Things-to-Do-After-Installing-Kali-Linux-on-Your-Computer

Identifiable

❤️35

python3 Kali Linux AutoInstaller

Python

Updated 1 year ago

extralinux10steps

georgeflanagin

🧡50

List of things to do in addition to the base install of Linux 10.x on workstations

MIT

Updated 1 month ago

Little-Fixes

Gheda133

❤️40

A collection of quality-of-life scripts that fix things, help you with stuff and provide useful utilities on Linux and Windows. Para que arreglarlo en 10 minutos si lo puedes automatizar en 10 horas 🤝

Python

Updated 1 month ago

Anndroid-studo-RAM-issue

hardikmodh123

❤️35

6 Answers active oldest votes up vote 34 down vote accepted You need to upgrade your PC though but there are few things you can do to make it faster 1. Increase the memory size of Android Studio: Open the file located at /bin/studio.vmoptions and Change the content from -Xms128m -Xmx800m to -Xms256m -Xmx1024m Xms specifies the initial memory allocation pool. Your JVM will be started with Xms amount of memory and will be able to use a maximum of Xmx amount of memory. Save the studio.vmoptions file and restart Android Studio. 2. Improve Gradle performance: Create a file named gradle.properties in /home/<username>/.gradle/ (Linux) /Users/<username>/.gradle/ (Mac) C:\Users\<username>\.gradle (Windows) and add the line: org.gradle.daemon=true This helps a lot, with org.gradle.daemon set to true Gradle reuses computations from previous builds and cache information about project structure, files, tasks etc. in memory so it won’t have to start up the entire Gradle application every time. Source shareimprove this answer edited Oct 10 '16 at 17:42 answered Apr 26 '16 at 10:45 Max 6,20732949 1 All these steps reduced the build time to 37 seconds. That's great performance improvement. Thanks. – Chandra Eskay Apr 26 '16 at 11:08 Your welcome :) – Max Apr 26 '16 at 11:40 Is it the Gradle Daemon that is making most of the difference? – Hackmodford Oct 7 '16 at 13:49 yeah it reuses computations from previous builds and cache information about project structure, files, tasks etc. in memory so it won’t have to start up the entire Gradle application every time. – Max Oct 7 '16 at 14:58

Updated 7 years ago

Minecraft-CRASH-when-i-enter-to-the-server-or-i-die-sometimes-Description-Exception-ticking-world-

elCohete

❤️35

Updated 4 years ago

How-to-share-data-

AdekoyaOlatolokikiAyomide

❤️35

Updated 1 year ago

All 20 repositories loaded

GitHub Explorer

Search Results

10-things-linux

HacksByLogout

Window

Install-OpenProject-Project-Managmen-Software-local-servert

CS344-OSI---Assignment-3-Small-Shell

10-things-to-do-AFTER-Installing-DEBIAN-LINUX

CS344-OSI---Assignment-3-Small-Shell

CouseraDatasharing

Bluetooth-Support-for-HP-14-Chromebook-Chroot

nemesis-current

w

10-things-linux

10-things-linux

RedHat-Enterprise-Linux-10-Post-Install-Guide

The-Top-10-Things-to-Do-After-Installing-Kali-Linux-on-Your-Computer

extralinux10steps

Little-Fixes

Anndroid-studo-RAM-issue

Minecraft-CRASH-when-i-enter-to-the-server-or-i-die-sometimes-Description-Exception-ticking-world-

How-to-share-data-

10-things-linux

HacksByLogout

Window

Install-OpenProject-Project-Managmen-Software-local-servert

CS344-OSI---Assignment-3-Small-Shell

10-things-to-do-AFTER-Installing-DEBIAN-LINUX

CS344-OSI---Assignment-3-Small-Shell

CouseraDatasharing

Bluetooth-Support-for-HP-14-Chromebook-Chroot

nemesis-current

w

10-things-linux

10-things-linux

RedHat-Enterprise-Linux-10-Post-Install-Guide

The-Top-10-Things-to-Do-After-Installing-Kali-Linux-on-Your-Computer

extralinux10steps

Little-Fixes

Anndroid-studo-RAM-issue

Minecraft-CRASH-when-i-enter-to-the-server-or-i-die-sometimes-Description-Exception-ticking-world-

How-to-share-data-