Plastic advisor tutorial pdf

This project is focused on the design of the gate size dimension for single cavity, analysis of the optimum gate size, analysis comparison of parameters pressure, velocity and temperature and the best material to be used for the selected optimum gate size dimension. The design of Plastic Name… Expand. Save to Library Save. Create Alert Alert. Share This Paper. Abstract This paper presents a new cross sectional shape of runner system in the injection molding.

The aim of the new geometry is to reduce the scrap and cycle time and also the easier ejection of … Expand.

Injection Molding. It is differentiated from compression molding, … Expand. Application of statistical process control on a matrix card holder production. The thesis deals with durability assessment application of quality control in our production of card holder. The objective of this thesis is to let l know what is the exactly feature when production … Expand.

Modeling in SolidWorks and analysis of temperature and thermal stress during construction of intake tower. Design and Molding Simulation of Plastic Part. Using this workflow, you have to tell Plastic SCM that you will perform a specific operation on a file.

In these scenarios, you'll use the very extended edit-checkin workflow , popular on most open-source version controls SVN, CVS, Git, and many others. In Plastic SCM, this is called transparent working mode because Plastic SCM can detect everything you've done in your workspace and propose it for checkin. Navigate to the Pending changes view to check what you've modified. The Pending changes view detects the files you've modified.

Because you didn't check them out before editing, the status value is Changed instead of Checked-out :. The next step is to move a file in your workspace and let Plastic SCM detect it. Move the lic. Note that this operation involves both the move and rename operations. Open the Pending Changes view. Plastic SCM detects the moved file, and the status is Moved locally. Note the Similarity column.

This column shows the percentage of similarity between files. Plastic SCM tries to match moved files with private files to determine if it's the same file. Only locally moved items have a value in this column:. But don't check it out:. This is what the Pending changes view looks like after moving the file:. Status is set to moved locally. After deleting the file, the Pending changes view looks like this:.

Note that the status column is currently set to Removed locally , which means that the controlled file was deleted from the workspace outside Plastic SCM. You can move directories in Plastic SCM. Plastic SCM identifies and displays only the directory that was moved instead of displaying all files inside as moved. At this point, you can Checkin in all the changes.

Don't forget to add a comment when you check in all files deleted and moved to document the change:. Navigate to the Branch Explorer to see the current state of the repository:. Now you see a comparison of the previous content with the current one. And, the diff looks like this:. In this lesson, you'll learn all about branches. Branches offer a way to isolate different lines of development from each other, often called Parallel Development.

The basic concept of a branch is a line of development that exists independently of another line and shares a common history. A branch always begins its life as a copy of something and moves on from there generating its own history. Branching is a very efficient process.

You can easily work with feature branches or go even further and use task branches, the model that Plastic SCM recommends. Plastic SCM implements task-driven development very efficiently through the well-known branch per task pattern.

To learn more, click the following links:. It's a snapshot of your code at a given point in time. It's a mark, a tag that you can use to rebuild this status later if you need to. Right-click the Labels view and select Create new label :.

In the New label dialog, enter the name and comment for the new label. This example uses Baseline01 for the name:. Note the Changeset to label field. It tells Plastic SCM where the label is applied. The default value is the current changeset loaded in the workspace. In this example, the changeset is number 7. Now, you've got another label to mark a stable release in your project.

Once the label is created, your Branch Explorer looks like this:. The current changeset on your workspace is represented with a house icon. Right-click this changeset and click Create branch from this changeset :. In the New branch dialog, enter scm for the branch name and a comment:.

This means that every development task is a new branch. Select the Switch workspace to this Branch checkbox to start development in the new Branch. Select the new branch and click the Options button in the toolbar. On the right, you will see the properties of the branch:.

Navigate to the Workspace Explorer to add the readme. Right-click the file and select Add to source control :. Navigate to the Pending changes view and check in the change to confirm the added file:. Now, modify the readme. First, check out the file and double-click to open it, or right-click the file and select Open.

Navigate to the Branch Explorer to check our new branch. Now you have two changesets in the scm branch: the first one you created when you added the readme. Now to add a new change in the branch. Navigate to the Workspace Explorer , checkout the lic. To modify it, delete lines 10 and 11 :. Navigate back to the Branch Explorer.

You can see a house with a dashed circle outline. This is the icon for checked-out changesets :. Navigate to the Pending changes view to see what you modified. Then, add a comment and run a Checkin :. If you go back to the Branch Explorer , you can see the current state of the current scm branch :.

The example above shows several checkins in the scm branch. If you checkin often, it will be easy for you to understand all the changes. This means that you are self-documenting the code. Lesson 5 covered working on the main branch, creating new branches, switching to them, and making changes. Navigate to the Branch Explorer and check the current status. To go back to the main branch, right-click the main branch and click Switch workspace to this branch :. Complete the steps to create another branch from the last changeset on the main branch:.

Check out the lic. Add a comment for example, Added new line and run a Checkin. Navigate back to the Branch Explorer to see the current state of your workspace:. Right-click the current branch and select the Switch workspace to this branch to return to the main branch :.

Right-click the scm branch and select Merge from this branch :. Click the Process all merges button at the top of the toolbar to process the merge:. Your first merge is complete! There aren't any merge conflicts. And the main branch contains the changes made on the scm branch. Navigate to the Branch Explorer to see the current status of the workspace:.

This is because you created a merge from the scm branch to the main branch, so a new changeset is going to be created after the checkin action.

You can now Checkin the changes from the merge. Don't forget to add a comment explaining the change. For example: Merge from scm branch to the main branch. Navigate to the Branch Explorer to see the current status of the repository:. Make a merge from scm branch to main branch.

If you want to dig deeper to learn more about the merge, click the Explain merge button at the top in the toolbar. The Merge explanation view looks like this:. Return to the Merge from branch view and click Process all merges. There is a new changeset pending check in so navigate to the Pending changes view and check the modified file. The Pending changes view lists the file you previously merged. Click the Show diffs button to see the line you've modified:.

You can inspect the difference before the checkin merge operation to ensure that the code has been correctly merged. Enter a comment for example, Merge from scm branch to main branch and click the Checkin button. A Baseline is a line that forms the base for any construction, comparisons or calculations. The objective of a baseline is to reduce a project's vulnerability to uncontrolled change by fixing and formalizing change by controlling critical points in the development life cycle. Baseline02 is where you would make up the Unit Tests that can help you ensure the code quality.

Navigate to the Branch Explorer and right-click the current changeset. Then, select Create branch from this changeset and enter scm as the branch name and add a comment:. Or right-click the main branch and select the Create child branch. Checkin the file. Don't forget to comment for example, Adding new conditions on DokanNet. Right-click the main branch and select the Switch workspace to this branch to return to the main branch:.

To create the second new branch from the Baseline02 label, navigate to the Branch Explorer , right-click the current changeset and select Create branch from this changeset. Enter scm as the branch name and add a comment:. Don't forget to comment for example, Adding new lines on DokanNet. Return to the main branch by right-clicking the main branch and selecting Switch workspace to this branch.

The current state of the repository looks like this:. Remember that you modified exactly the same section of code in the same file. This action makes the merge much more complicated. To perform this merge, first, you'll merge from the scm branch to the main branch.

Then, you'll merge from the scm branch to the main branch. Start by going to the Branch Explorer. Then, Right-clicking on the scm branch and click Merge from this branch. Currently, there changes are only in the source contributor. Click Process all merges and the merge will run automatically.

Navigate to the Branch Explorer to check the current state of the workspace:. There is a new pending merge link so go to the Pending changes view. Don't forget to write a comment for example, Merging from scm to main before running Checkin :.

In the Branch Explorer , right-click the scm branch and select Merge from this branch. In the Merge from branch , click Process all merges. Mergetool window:. You can see the code added in the scm branch source , and the scm branch destination. At the bottom, you will see the final result with both contributors. If you agree with the Destination , click Deselect Source :. Once you've reviewed the file, click the Save and Exit button at the top of the toolbar.

In the Pending changes view, you can check the file you've modified. Remember to add a comment before you Checkin :. The last scenario followed a 3-way merge.

This involved modifying the same file in the same place in two different branches. The resulting file is the one created after the changes are combined , and you decided which would be the final code. A 2-way merge is more straightforward because it doesn't consider the base file common ancestor to calculate the merge. Then merge the code with the 2-way merge tool. Check out the results in the figure below:. Set up Plastic SCM. Review the fundamental concepts of Plastic SCM.

Visit the Plastic SCM download page. Explore the More installers , Previous releases or Labs downloads links to download the last release, or any other release.

You can: Download a 5-day free trial license. Sign up to get a day free trial license for 5 users you will receive an email with the download instructions. But, as an administrator, you can configure the server with the required settings. The user's credentials. Here are a few concepts that you'll need to know: Repository The repository typically contains a project: Workspace The directory where you store your sources: Items The content of your workspace - files and directories: Branch The place in the repository where you're currently working.

You can create new branches then switch to them, compare their content, merge them, replicate them, and much more: Changeset The individual checkin you made: Label A label is a name assigned to a specific changeset.

This lesson covers: The basic structure of a repository and a workspace. How to add your code to the version control, configure the ignored list and create your first label. Windows - Create a new repository.

Linux - Create a new repository. Mac OS - Create a new repository. Windows - Create a new workspace. Linux - Create a new workspace. Mac OS - Create a new workspace. Complete one of these steps to update the workspace with the downloaded code: Right-click the new changeset click Switch workspace to this changeset. Or, select the branch and click Switch workspace to this branch.

Right-click the current changeset circle with the house icon and click Label this changeset : Enter BL00 in the label name field and enter a comment: Your Branch Explorer looks like this: Labels are used to mark stable releases in your project. Plastic SCM detects that the file has been modified which is good for quickly locating changes. To checkout, right-click the file and select the Checkout menu option: Plastic SCM marks the file as checked-out :.

Right-click the obj folder and click Add to ignored list , and select the obj option: To add every obj folder in all your workspaces to the ignored list, select the Apply rules to all workspaces checkbox: Repeat the process for the bin , and you see something like this: You can add private items to the ignored list.

Run a checkout and open the file you want to edit. Navigate to the Pending changes view to see the files you've modified so far: The Pending changes view lists the files you previously checked out. Click the Show diffs button to see the line that you modified: The Show diffs button allows you to inspect the differences in every file before checking them in.

You see something like this: In the branch, there are now three changesets: The initial changeset The changeset with the label Baseline00 above it The current changeset house icon Right-click the current changeset.

This window has three sections of information: Top - Information about the changeset and its author, and the comment you wrote upon check in Middle - The list of items being compared Bottom - The diffs between the current changeset number 2 or cs:2 and the previous number 1 or cs:1 changeset.

In this lesson, you'll be able to move, rename, and delete a file. After you perform this operation, your Workspace Explorer looks like this: The Pending changes view shows what you've modified so far: The picture above explains the steps you just performed: source and destination of the move and the status changed to moved. In Mac OS: If you want to remove a file from the version control but want to keep it in your disk like a temporary file that you mistakenly added , select the Remove item s from version control option.

In Linux: If you want to remove a file from the version control, but want to keep it in your disk like a temporary file that you mistakenly added , select the Remove item s from version control option.

The Pending changes tab looks like this: Notice the file is listed twice: One instance is Added - The status is Private the file is kept on the disk as per the previous step. Second instance is Deleted - The status is Removed removed from version control. This means that the file is not under source control anymore, and it is displayed without a customize icon and no entry in the Type, Branch, or Changeset columns: If you switch to the Pending changes view, you can Checkin the deleted item.

Right-click the file you wish to rename and select Rename : Enter a new name: The Pending changes view now looks like this: Notice that the status of the file has changed to Moved. Checkout the file and add the following edits: Save the changes and navigate to the Pending changes view to see the modified file.