Skip to main content

    Filter by idea status

    Filter by product

    3 Ideas

    Newcomer
    adamjamesNewcomer

    How Custom Digitizing Helps Control Fabric MovementNew

    Fabric movement is one of the main reasons an embroidery design may not stitch exactly as it appears in digitizing software. The artwork may be perfectly centered, yet the finished logo can look slightly different. Understanding pull and push compensation helps explain why these changes happen and how a digitizer can prepare for them.Fabric Does Not Stay Completely StillDuring stitching, the needle enters and leaves the fabric thousands of times. Thread tension also creates movement.The result can include:Stretched edges Narrow columns Shifted details Uneven lettering Misshaped circlesThese issues become more noticeable when a design contains dense areas or small details.The Role of CompensationPull compensation is useful when stitches pull fabric or narrow a design element. The digitizer can slightly increase the width of selected areas so they have a better chance of reaching the intended size after stitching.Push compensation deals with the opposite type of movement. Dense stitching can push fabric outward, changing the shape of an element.This is one reason custom embroidery digitizing service work should be based on the actual fabric and finished application rather than artwork alone.Small Designs Need More CareSmall logos and lettering leave little room for mistakes. A minor change in width can affect readability.A skilled digitizer considers:Letter height Satin stitch width Stitch density Underlay structure Fabric stability Stitch sequenceThese decisions work together. Compensation cannot fix every problem by itself.Test Before Large ProductionA sample run is useful when preparing an important logo or garment order. The test can show whether the design needs changes in width, density, underlay, or stitch direction.If the sample shows a narrow column, the digitizer can adjust it. If a filled area spreads too much, the structure can be changed.A Practical ApproachGood digitizing is about preparing for what will happen after the needle starts moving. Pull and push compensation is one part of that process, but it works best when combined with suitable underlay, stitch direction, density, and sequencing.The goal is simple: create a design that behaves well on real fabric, not just one that looks good on a computer screen.https://blogotypo.moinnaik.in/blog/how-push-and-pull-compensation-saves-your-embroidery-projects  

    0
    Newcomer
    Forum|Forum|21 days ago
    jmansheim
    Novice I
    jmansheimNovice I

    Has anyone figured out a way to create resident vacation check reports in M43?New

    Hi allOur agency serves a small town of 2,000 people.  We still provide vacation checks to our residents.  If they go on vacation, they can submit a form to us and we will either do a drive by or go around and check windows and doors, depending on their request. I would really like to be able to enter these vacation checks in M43 and then use the data lake access to run a daily report against any active vacation checks.  For instance, create a new report type called “Vacation Check” and set the event start date/time as the start date of the vacation check and set the event end date/time as the end date of the vacation check.  Then create a data lake report that pulls out any requests that are active based on when the report is run.The challenge, so far, is M43 does not allow future dates in the start/end dates for reports, at least as far as I know.Has anyone else run into this type of need and found a way to do it with M43?

    6
    Contributor II
    Forum|Forum|4 years ago
    Contributor II
    Jaycee.ElliottContributor II

    Enhanced Validation Criteria for Unknown Race EntriesNew

    I came across the hyperlinked article in The Seattle Times this morning and it echoed exactly what we are experiencing with our tenant of Mark43. Ironically, I was presenting our quarterly use of force data to command staff and we again discussed the prevalence of subjects with “Unknown” race entries on the contextual profiles of use of force reports, despite the same subject having previous contacts and a known race listed.  Report: Use of force by Seattle police at all-time low, but racial disparities cloud numbers | The Seattle Times Unfortunately for Seattle PD (as this article reads), the monitor over their consent decree will not support the lifting of the decree, in large part due to the failure to reliably document the race of subjects in use of force incidents. For those that do not know, Seattle PD uses Mark43.  I have proposed this numerous times previously and have attempted to both demonstrate and discuss the significance of this issue, but it has gained little to no traction. Hopefully others here have noticed the same thing and we can collectively discuss and propose solutions to Mark43 for enhanced data collection. Proposal:Maintain the ability for “Unknown” race to be entered. This is necessary for true unknowns and to report to NIBRS. Add additional validation criteria for profiles that have “Unknown” race. Oftentimes, the race of a subject is prefilled from any number of sources (i.e., historical reports, disparate interfaces, related reports under the same REN, etc.). These instances often result in passive acceptance of the prepopulated data elements, that perpetuate the issue. In any case, passive (or intentional direct entry) of “Unknown” race subjects, I would like the author to receive a prompt that forces them to go back to that data element and select a known race or maintain the “Unknown” entry and populate a free-form text entry explaining/confirming a reason for the entry.   Would love to hear the thoughts of other Mark43 clients and Mark43.   

    0
    Contributor II
    Forum|Forum|4 years ago

    Filter by product

    • All products
    • Analytics
    • CAD
    • RMS
    Terms & ConditionsAccessibility statement